Claude Design just cut 60% of your designer's week — here's what to do with the rest + 4 prompts

Claude Design shipped April 17 alongside Opus 4.7, in research preview. The coverage split cleanly. One camp: Figma’s stock dropped 7% and commentators argued about what that means for the design software industry. Another camp: the tool has real rough edges and commentators argued about whether those break the story. Both frames miss the point.

Sometimes a product ships with warts and the warts don’t matter. Anthropic has a pattern of shipping those. Claude Code was the first. Cowork was the second. Claude Design is the third, the one that makes the strategy finally clear.

All three do the same structural work: intent goes in as natural language, a working artifact comes out, and it hands off directly to the next product in the stack. With Design, the last big category of production work — visual artifacts, the thing every product team makes first and shows to everyone — joins Code and Cowork inside the same pipeline. The prototype isn’t an approximation of the thing anymore. It’s the thing, or one handoff away from it.

Brilliant told Anthropic that its most intricate product pages used to require twenty or more prompts to recreate in competing tools. In Claude Design they need two. Datadog compressed a week-long cycle of briefs, mockups, and review rounds into a single conversation. Earlier this year a Jane Street designer wrote publicly that he now designs in Claude more than in Figma, building working prototypes directly in the codebase instead of making Figma mocks that describe what the code will eventually do. Those aren’t demos. They’re practitioners describing what happens when the mockup-to-production handoff — the twenty-year-old ritual where designers make pixel approximations that engineers then rebuild in code — gets replaced by one conversation that produces the actual UI in the medium it will run in. Most of how your team is structured was built around that ritual. It isn’t the ritual anymore.

Here’s what’s inside:

• Three products, one bet. How Code, Cowork, and Design work the same way, and why the third one is the piece that makes Anthropic’s strategy finally legible.

• Eight things you can actually make. Pitch decks with live embedded AI, 3D configurators, design systems extracted from your codebase in twenty minutes, and five more — each one replacing a tool, a specialist, or a queue.

• Figma, Stitch, and the medium war. Why LLMs ended up working in code and markdown instead of Figma files, why Mike Krieger stepped off Figma’s board three days before launch, and why Google and Anthropic are making opposite bets on what it all means.

• What changes, role by role. Where PMs, designers, engineers, and founders have to move their craft upstream — and which parts of the two-pizza team stop making sense.

• Grab the prompts. A design system extractor that makes Claude Design stop guessing your brand, a prototype sprint that generates every UI state your team usually forgets, an org audit for roles built around costs that just vanished, and a migration decision tree for what stays in Figma.

The warts are real. They’re also the least important thing about what shipped.