Anthropic moved Claude Design into Claude itself this month. New Slides and Design projects are created as artifacts, and design systems are a managed asset you migrate once and use across every artifact and every session.
Here’s why that matters, from experience. Claude Design has been a capable tool that lived in the wrong place. It was standalone, disconnected from where the actual work happened, and hard enough to reach that most people on a team never touched it. Our workaround, like a lot of teams’ workarounds, was to rebuild the brand as instructions. We wrote skills in chat and Cowork that taught Claude our palette, our type, and our rules so that everyday drafts came out close to right without anyone opening a separate design product. It worked. It was also duct tape, hand-maintained and living outside any real design file.
This update makes that layer unnecessary. When the design system is native to the surface where documents, decks, and pages get drafted, the system does what the hand-written instructions were doing, everywhere, for everyone, without being re-taught. Which changes where your time should go. The effort teams spent on workarounds now belongs in the design system itself, because whatever you migrate is what every fast draft will inherit. A sloppy design system used to be a private problem. Connected to the tool your whole team drafts in, it reproduces.
So before you migrate, make it right. What that means in practice.
Give every token a rule, not just a value. Don’t migrate a hex code. Migrate “this red is for calls to action only, never headings, never decoration.” A generator that knows your colors but not your rules will use them everywhere. The values it can read off any old slide. The judgment is what you’re actually encoding.
Cull the icons. Generators amplify inconsistency. If your icon set carries three eras of styles, every deck becomes a sampler of all three. Migrate the one consistent set, name icons by function, and state the style rule so anything drawn new comes out in the same hand.
Curate images like a photo editor, not a librarian. Twenty images you would put on page one of a client deliverable, with usage rights you’re certain of and your treatment standard stated. The design system is a palette, not an archive. Everything in it is something the tool will consider leading with, under your name.
Migrate logos with their never list. Every lockup, minimum sizes, clear space, approved backgrounds, and the misuse rules. Never stretched, never recolored, never on busy photography. Misuse rules are the part generators need most and are given least.
Templates are the highest-value asset in the system. Build them for what your team reproduces weekly. A deck kit of about seven slides covers most requests: title, section divider, single-idea content, data, quote, team, and closing. Add the one-pager, the case study layout, a proposal cover, and your core social sizes. Two rules make templates survive a generator. First, declare locked zones and variable zones: the logo, margins, and footer never move, while the headline, body, and image slots do, and every variable zone needs an overflow rule for the day the headline runs long, because it will. Second, name templates by job, “client proposal cover,” never “blue layout 2.” The generator picks by name, so the name is the instruction.
Then test it like software. Ask for the same three deliverables cold: a deck, a one-pager, a social card. Grade them. Every miss reveals a missing rule. Fix the system, not the output, and run it again. Two or three rounds gets it honest.
And give it an owner. The design system now propagates to everything the whole team drafts. An edit to it is a deploy, so someone approves changes, and it isn’t everyone.
The pattern from two years of AI tooling holds here. Drafts keep getting cheaper, and judgment keeps getting more valuable. This month, the place to put that judgment is your design system, because for the first time it will pay out everywhere at once.
We’re migrating ours now and testing it against real deliverables. If yours is a PDF nobody opens, this is a good month to fix that, and it’s work we do with clients every week.
