Why your Claude Design slides look generic (and the 3 files that fix it)
Learn the exact prep work that makes Claude Design output polished, on-brand slides instead of generic templates every beginner gets stuck with.
Most people open Claude Design, pick a template, type a quick description, and hit generate. Then they stare at a deck that looks like every other AI-generated presentation out there — same gradients, same layout, same forgettable feel. It's not that Claude Design is bad at its job. It's that nobody told Claude what "good" actually looks like for your brand before asking it to build something.
The fix isn't a better prompt. It's three files prepared before you ever touch the generate button: a DESIGN.md file, a native design system built inside Claude Design, and a reusable slide template. Get those three things in place once, and every deck you make afterward comes out polished, on-brand, and consistent — without you writing a paragraph of styling instructions every single time.
What is Claude Design, exactly?
Claude Design is Anthropic's built-in visual creation tool, and it's part of Claude.ai rather than a separate product. It lets you create polished presentations and slide decks directly through conversation, and it's become one of the most popular use cases internally at Anthropic, enabling teams to build professional decks in minutes rather than hours.
The magic isn't just that it can generate slides — plenty of tools do that. The real value is that if your organization has set up a design system in Claude Design, your slides automatically apply your brand's colors, typography, and visual style, which ensures consistent branding across all presentations without manual tweaking. That's the entire premise behind the three-file setup: do the brand thinking once, and let Claude reuse it forever.
You'll need a paid plan to access it. Go to claude.ai/design directly in your browser, or open the Claude desktop app and navigate there — you need a Pro, Max, Team, or Enterprise plan.
Why does skipping the prep work make your slides generic?
Jumping straight into a template and prompting away feels efficient, but it backfires. Without a defined design system, Claude has to guess at your visual identity every single time you generate something, which means it defaults to safe, generic choices — the same soft gradients and stock layouts you've probably already seen in a dozen other AI-made decks. You end up burning extra tokens and time re-prompting to fix things that should've been locked in from the start.
The three-file workflow flips that. Instead of describing your brand from scratch in every conversation, you build the brand context once and let Claude reference it automatically going forward.
What is a DESIGN.md file and why does it matter?
A DESIGN.md file is just a text file that spells out the rules for a design: the exact colors, fonts, spacing, and how things like buttons and cards get styled. It works in any AI tool, so Claude Design can take it and turn it into its own native format.
Think of it as the translation layer between "what your brand looks like" and "what an AI model can actually act on." A DESIGN.md file is a communication layer between your design system and a model, and it needs to be written for that purpose specifically — not as a style guide export, not as a token dump. The tokens (colors, fonts, spacing values) are the easy part. The tokens are the easy part — for you and for Claude. The brief, the intent, the constraints, the don'ts — that's the work.
The good news: you don't need to write one from scratch. You don't need to write one from scratch — grab a public one from the awesome-design-md GitHub repo, then clean it up so it's safe to use. The awesome-claude-design repo on GitHub is a solid place to start, offering dozens of ready-made design system inspirations in DESIGN.md format that you can adapt to your own brand. DESIGN.md is a single plain-text markdown file that describes a brand's visual language in a format AI agents can actually act on.
Once you've grabbed a template file, run it through a cleanup pass. Paste it into ChatGPT (or any chatbot) with a prompt asking it to remove the proprietary and licensed content from the file and replace it using its own judgment. This keeps you from accidentally shipping someone else's copyrighted brand language baked into your deck.
How do you turn that file into a Claude Design system?
Once your DESIGN.md file is cleaned up, it's time to upload it into Claude Design itself. You upload it by going to claude.ai/design, clicking Create new design system, and on the Set up your design system screen, uploading the DESIGN.md under Add assets.
From there, Claude takes over the heavy lifting. Give it a short name and description, then scroll to the bottom and upload your cleaned DESIGN.md file — this takes 10 to 20 minutes while Claude Design reads your file and generates real mockups to review. You're not just uploading a static file — you're watching Claude turn that markdown into an actual living design system with tokens, components, and preview assets. Instead of generating one-off screens in a chat window, it holds a persistent design system for your project: tokens, components, and preview assets you can actually ship. You give it a starting point — an aesthetic, a vibe, or a DESIGN.md — and it scaffolds the system: color tokens, type scale, buttons, cards, nav, and a working UI kit.
Once it's done generating, you're not locked in. When it's done, you can change anything with the "Feedback" button in plain English. This is where you catch anything that doesn't quite match — a color that's slightly off, a font pairing that feels wrong, spacing that's too tight.
Want to push it further? Upload extras beyond just the design tokens. Optional but worth it: upload a few extras to customize the system further, like a voice principles file so the copy sounds like you, plus your logo and the icons you reuse — after that, every future design pulls them in automatically. This is the step most beginners skip, and it's exactly why their AI-written slide copy sounds nothing like them.
How is a template different from a design system?
This distinction trips a lot of people up, so it's worth spelling out clearly. A template is a pre-built deck in your style that every new presentation starts from: title slide, section dividers, a two-column layout, and so on — the difference between them is simple: the design system controls how everything looks (colors, fonts, logos), and the template controls the structure and flow of the deck itself.
In other words: the design system is your brand's DNA. The template is the skeleton every new presentation gets built on top of. You need both. A design system without a template still leaves Claude guessing at layout decisions every time. A template without a design system just repeats the same generic look with a different arrangement of boxes.
Build a slide-deck-specific template once — a title slide, an agenda slide, a two-column comparison layout, a section divider, a closing slide — and every future presentation starts from that skeleton instead of a blank page.
What can you actually do once these three files exist?
This is where the setup pays off. On the Claude Design homepage, you select your design system, then select the matching slide template, and then attach your actual content — talking points, an outline, whatever raw material you're working from, usually in simple markdown format. Then you just ask Claude to turn that content into slides using the system and template you've already built.
Anthropic's own team uses this exact workflow internally. Teams at Anthropic are using Claude Design presentations for meeting prep decks with customer-specific branding — to create a presentation, simply describe what you need in your prompt, and be specific about your audience, key messages, and any organizational context that should influence the design. With a design system and template already loaded, most of that context is already baked in — you're just supplying the content.
Editing afterward is conversational, not manual. You refine through conversation, inline comments or direct edits until it's right — you can ask Claude to shorten a slide, reorder sections, rewrite a headline or adjust the visual layout. There's also a difference between global feedback (changes to the whole deck) and what you might call surgical, slide-level feedback — tweaking one specific slide without touching the rest. Claude Design supports referencing individual slides directly in your message so you're not accidentally triggering a full-deck regeneration when all you wanted was to fix one bullet point.
How do you export the finished deck?
Once the deck looks right, exporting is straightforward and flexible. When you're satisfied with the result, export the file — export options include PDF, PowerPoint (.pptx), standalone HTML and ZIP, and you can download the .pptx to open and edit it in PowerPoint like any other file. Some setups even push directly to Canva if that's where your team does final polish. Founders and Account Executives can go from a rough outline to a complete, on-brand deck in minutes, and then export as a PPTX or send to Canva.
Does this workflow work for anything besides slides?
Yes — and this is worth knowing before you invest time building your first DESIGN.md file. Even though the focus is often on slides, the same workflow applies to social carousels, newsletters, and any other design. Once your brand's design system exists inside Claude Design, you can point it at almost any visual asset — landing pages, marketing graphics, product mockups — and get output that already matches your brand without re-explaining it. Marketers can create landing pages, social media assets, and campaign visuals, then loop in designers to polish.
Where should you start?
Head to claude.ai/design and check Anthropic's own tutorial on using Claude Design for presentations for the official walkthrough. Then grab a starter DESIGN.md from the awesome-claude-design GitHub repo, clean it up, and build your design system before you generate a single slide.
The deck you make on day one with this setup won't look like the deck everyone else is making with the same generic template-and-prompt approach. That's the whole point — and once the system exists, every future presentation is just content-in, brand-consistent-deck-out.