Claude Design is Anthropic's design tool, currently in beta. You describe what you want in a chat on the left, and it draws it on a canvas on the right while you correct it: presentations, one-pagers, prototypes, marketing collateral. You can export to PDF, PowerPoint, HTML, or a link you share inside your organization. It's built for people who need professional-looking material and don't have a designer sitting a desk away.
Why we're writing this one
Naty's telling this one. We picked up Claude Design on August 11 for the look of our carousels, and the first batch came back in a flat typographic style that wasn't ours. It wasn't bad work. It just wasn't us. We hadn't uploaded a single reference.
Here's the part I'd rather not admit. We then put our best presentation into a project, got a much better result, and moved on believing the tool knew our brand. It didn't. What we'd done helps one piece. The thing that fixes all of them sat somewhere else, behind a toggle we never touched.
To be straight about the timing: this is our monthly tools slot, not this week's news. Both Anthropic support pages behind this article are dated August 6, and we checked them September 13. We could have dressed it up as brand new. It isn't. What makes it worth a Tuesday is that the part which changes your output has been public for over a month and the setup lives where nobody looks, which is why the first thing most people do instead is attach a file to a project. We did.
What actually changed
The feature that matters is the design system. You give Claude Design material that represents your brand, and it pulls out reusable pieces: your color palette, your font families with sizes and weights, components like buttons and cards, and layout patterns, meaning spacing, grids and page structure. From then on, that's the foundation for projects created in your account.
What it takes as a source is more generous than you'd expect. A codebase, if your website was built by a developer. Design files. Loose uploads. Anthropic says even a well-made PowerPoint or PDF that reflects your brand can work, which for most service businesses is the realistic answer, because the closest thing you have to a brand guide is one good deck.
Anthropic is blunt about the catch, in their own known limitations: "Design system import is only as good as its source. A messy codebase or an incomplete file will show up in the output." It reads what you hand it.
And here's what that means for how you read your own results: what you publish is the only proof anyone has of how you work when they're not watching. What looks like it's working and what's actually working aren't always the same thing.
How to set it up, step by step
Before you start, Anthropic lists two prerequisites: permissions granted by your organization's admin, and at least one source file.
- Create or switch to your organization. Open the tool, click the current organization name in the lower left corner of the project picker, pick yours or create a new one, then finish the onboarding flow.
- Upload your brand and product assets. During onboarding, or later from organization settings. One source is enough to start. More gives it more to work with.
- Review what it generated before you build on top of it. It comes back with a palette, typography, components and patterns. Anthropic's way to check: create a test project and ask for something simple, like a landing page for your product, or a presentation on a topic your team presents often.
- Turn on the "Published" toggle. This is the step. Until you flip it, what you built does not become the base of new projects. Everything above can be done perfectly and still change nothing.
To edit it later: organization settings, "Open" next to the system, then "Remix", which opens a chat where you can modify it.
Copy this, and paste it with your file
Anthropic's guidance on writing a good request: include the goal, the layout, the content and the audience. Their line is "You don't need to be a designer to get great results."
Here's a fill-in version built for this job. Paste it alongside the file you're uploading, and fill in the brackets in your own words.
I'm setting up our design system in Claude Design.
The file I'm uploading: [file name]
Why this one: [it's the piece we send out most / the last thing a
client told us looked professional / the only file where the logo,
the colors and the type are all correct]
EXTRACT from this file:
- the exact colors, with their codes, and where each one is used
- the fonts, with sizes and weights, for headings, subheads and body
- the button, card and table styles
- the spacing and the page structure
DO NOT extract:
- [the stock photos / the placeholder text / anything on page X]
- [any color that only shows up inside a chart]
Rules that are NOT in the file:
- we never use [color], anywhere
- headings are written in [sentence case / title case / all caps]
- our tone is [plain and direct / warm / formal], and we don't use
exclamation points
- we're talking to [describe the person in your own words, the way
you'd describe them to a new hire: "a practice owner reading this
between patients, with about four minutes"]
BEFORE you build anything, report back:
1. every color you pulled, with its code and the page or section
it came from
2. every font you pulled, with sizes and weights, and where you
found it
3. anything you could not find and had to guess
Wait for me to confirm that list before you produce a single slide.
That last block is the part people skip, and it's the part that pays. Making it show its work turns a silent guess into a list you can correct in thirty seconds.
Four things worth knowing
Ours, and we're stating it as what we saw, not as proven cause. Our first batch came out in a flat typographic style that wasn't ours, and we hadn't uploaded any reference. We can't prove one caused the other. What we can say is the output had a voice, it wasn't the one we'd have picked, and we'd given it nothing to go on.
Ours, and this is the expensive one. We put our best presentation inside a project, saw a good result, and concluded the system was set up. It wasn't. A good result on one piece is not evidence that the account is configured. Go look at the toggle.
From the documentation. A good request has four parts: the goal, the layout, the content and the audience. Most requests people type have one, the content. The other three cost a sentence each.
From the documentation. Design activity draws from the same usage pool as your normal chats, and projects with many iterations consume more. A deck you refine twenty times spends from the same bucket as everything else you do that day.
What it does badly
Collaboration is thin. Anthropic's known limitations say two people editing at once is still basic, and that inline comments sometimes don't appear. Their workaround is to paste the comment straight into the chat, which works, and also tells you how early this is.
Then there's the dependency. The system you build lives inside a product that isn't yours and is in beta. That's not a reason to avoid it. It's a reason to keep the source file in a place you control, the same argument we made about where your client data actually lives. The design system is a derivative. The file is the asset.
And Anthropic's own limitation bites hardest: the import is only as good as the source. If the deck you upload carries three near-identical blues because nobody ever decided, you get three near-identical blues back, in everything.
The honest gap
The whole setup is written around an organization and a team. Step one asks you to create or join one. The prerequisites require permissions from that organization's admin. And when Anthropic explains that projects inherit the design system after setup, they add, in parentheses, "for Team and Enterprise plans."
So what happens if you're a business owner on a solo Pro plan with no team? Their documentation doesn't say. It doesn't say you can and it doesn't say you can't. We haven't tested it on an individual account, so we won't guess either way. We owe you that test, and you'll read the result here.
On access: Pro, Max, Team and Enterprise, not the free plan. Web and desktop only, no mobile. On Enterprise it's off by default and an admin switches it on.
Who should skip it
If you produce one document a quarter and it already looks the way you want, skip this. A design system pays off across volume, and without volume you'll spend an hour to save fifteen minutes. Same if you have a designer and a real brand manual they follow. You don't have a consistency problem.
Where this lands in your business
If you run a dental practice, a law firm, a marine shop, a restaurant or a med spa, the material that decides things for you is small and repetitive: the proposal, your price list, the treatment explainer, the estimate, the one-pager you hand somebody in the lobby. Those get made by different people at different times, and they drift. The client never says "your fonts don't match." They just trust you a little less and can't tell you why.
That's the real use. Not prettier slides. Making the fifteen things that leave your office look like they came from the same company, without a meeting about it. And the order matters: if you've never sorted out the five disciplines map, start there, because consistent collateral makes a strong position land harder and does very little for a position nobody can find.
The one thing to do this week
Under thirty minutes, and you don't need the tool to do it.
If it wasn't a clean yes, your decision this week is which of the two is the good one. That file becomes your source, whether or not you ever open Claude Design.
Keep reading
- Cited or bought - what your published work says about you
- Where your client data actually lives - why the source file matters more than the system built from it
- The five disciplines map - where consistent collateral fits in the bigger picture
- Get started with Claude Design, Anthropic support
Sources
- Claude Design product page,
https://claude.com/product/design- what the tool is, beta status, plans and availability - verified 09/13/2026 - Get started with Claude Design, Anthropic support,
https://support.claude.com/en/articles/14604416-get-started-with-claude-design- how a request should be written, plan and platform availability, usage pool, known limitations - verified 09/13/2026, page dated 08/06/2026 - Design system setup guide, Anthropic support,
https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design- the four setup steps, the Published toggle, what the system extracts, accepted sources, Team and Enterprise inheritance note - verified 09/13/2026, page dated 08/06/2026 - Hub365 AI own use - adopted 08/11/2026 for carousel design. Two observations reported as observations, not proven cause: first batch returned in a style that was not ours with no reference uploaded, and a reference file attached inside a project was mistaken for a configured design system
