I have tried most of the AI tools that claim to make presentations. The results were always the same: slides that looked like AI made them, layouts that fell apart, text that did not fit, designs nobody would actually use in a real meeting. The workflow was always “AI makes something, I spend an hour fixing it.”
Claude is different, but not automatically. The quality of what comes out depends almost entirely on how you set it up. Do it wrong and you get the same generic output as everything else. Do it right and 30 slides take about ten minutes, and they look like a designer touched them. Here is exactly how to do it right.
Step 1. Pick Your Design Style Before You Write a Single Prompt
Most people skip this step and jump straight to prompting. That is why their results look inconsistent. Before you open Claude, decide on your design direction: the color palette, the overall feel (minimal, bold, corporate, creative), and the visual hierarchy you want across slides.
A useful tool for this is getdesign.md, which lets you browse and select design systems before bringing them into Claude. The key is having a specific visual reference in mind — not just “professional looking” but actual hex codes, font choices, and layout principles. Claude works much better with concrete specifications than with vague aesthetic descriptions.
Once you have that decided, write it down somewhere. You will reference it when building your prompt in the next step.
Step 2. Build the Design System Prompt
This is the most important step, and the one that takes the most thought upfront. You are not writing a prompt to make one presentation. You are writing a design system that Claude will apply consistently across every slide it makes.
The prompt needs to cover these things explicitly:
- Font: specify exactly one font family and stick to it. Mixing fonts is where AI-generated slides break down visually.
- Slide format: 16:9 only. Never let the output vary between formats.
- Layout consistency: chapter names, titles, and subtitles should appear in the same position on every slide. If they drift around, the presentation feels chaotic.
- Content density: explicitly tell Claude to fill the lower portion of slides rather than leaving it blank. Empty space in AI-generated slides looks like an error, not a design choice.
- Logo and branding: if you have a specific logo or brand asset, specify where it appears on each slide.
- Language: keep the prompt language consistent throughout. Switching between Korean and English mid-prompt causes inconsistencies in the output.
Here is an example of what this prompt structure looks like in practice:
“You are a professional presentation designer. Apply these rules to every slide you create: Use only [your chosen font] throughout. All slides are 16:9 format. Chapter names appear in the top left, titles centered below them, subtitles directly beneath the title — same position on every slide. Fill the lower section of each slide with relevant content, diagrams, or visual elements — do not leave large empty areas. Place the logo in the bottom right corner of every slide. Write all output in English.”
This prompt is what you save in your Claude Project (covered in Step 4). Once it is set, you never have to rewrite it.
Step 3. Fine-Tune the Output on Your First Slide
Ask Claude to generate just the first slide or the title slide first. Look at it carefully. This is where you catch the issues that would otherwise appear across every single slide in the deck.
Common things to fix at this stage: the font size hierarchy is off (titles and body text too similar in size), the layout is shifting slightly between elements, the color contrast does not work as expected, or the content density is either too sparse or too crowded.
Fix each issue by adding a specific instruction to your base prompt. Not a vague instruction like “make it look better” but a concrete rule: “title font size should be 36pt, body text 18pt, no exceptions.” Then regenerate the single slide and check again.
Once slide one looks exactly right, generate the full deck. Because Claude is applying consistent rules, everything else follows the same pattern. This is why the ten minutes figure is realistic — most of that time is on the first slide, and the rest generates fast.
Step 4. Save Everything in a Claude Project
This is the step that turns a one-time workflow into a permanent system.
In Claude, go to Projects and create a new project called something like “Presentation System.” Paste your finalized design prompt into the project instructions. Upload your brand assets — logo, font files, color palette reference — into the project knowledge base.
From this point forward, every conversation you start inside this project automatically has access to your design rules and assets. You do not re-upload anything. You do not re-explain the style. You just describe the content of the presentation you need and Claude applies the system you already built.
This is also why the project setup step is worth spending time on properly. A poorly configured project saves you nothing. A well-configured one means every future presentation starts from a strong foundation rather than from scratch.
Step 5. PDF to PPT and PPT to PPT
Once the project is set up, two workflows become very useful.
The first is PDF to PPT. If you have a report, research document, or NotebookLM output saved as a PDF, upload it into the project conversation and ask Claude to convert it into a presentation. Claude reads the document, identifies the natural chapter structure, pulls out the key points for each section, and generates slides following your design system. A 20-page research PDF becomes a structured deck without you deciding what goes on each slide.
The second is PPT to PPT. If you have an existing presentation with solid content but weak design, paste the text content into the project and ask Claude to rebuild it using your design system. The structure and information stay intact, but the visual output matches your style rather than whatever the original used.
Both workflows benefit from the project setup. Without it, Claude does not know what your design standards are and defaults to generic. With it, the conversion output looks like something you would actually use.
The Part That Still Requires You
Claude generates the slides. It does not generate the thinking behind them.
The narrative structure of a good presentation — what argument you are making, what the audience needs to understand by the end, what order information should come in — those decisions still require judgment that Claude cannot make for you. It will organize whatever you give it, but if the underlying thinking is muddled, the slides will be muddled slides with good typography.
The workflow works best when you arrive with a clear outline of what the presentation needs to accomplish. Claude handles everything from that point forward — structure, layout, design, density, consistency. But the outline is yours to build.
That division of labor is actually the right one. The parts of presentation work that are tedious and time-consuming — getting the design consistent, filling slides without leaving them half-empty, reformatting content from other documents — Claude does those quickly and well. The part that requires actual expertise, knowing what you want to say and why, stays with you. That is how it should be.
Leave a Reply