Claude Design has the incumbents scrambling

Google released Stitch 2.0 on March 20, 2026. It shipped with an infinite canvas, multi-screen consistency, voice input, a Direct Edit feature, an MCP server, and a path to AI Studio for handing off to development.

Anthropic shipped Claude Design a month later. I don’t know if that was a reaction to Stitch, and maybe it doesn’t matter. In the battle for the desktop, Google and Anthropic are going at it fast.

My read is that Anthropic already had the product in hand and waited to ship it alongside Opus 4.7. Maybe I’m wrong. Either way, the sequence says a lot. Krieger steps off Figma’s board, and three days later Anthropic ships Design. That’s a real commitment to an already crowded category of generative design tools.

Who actually needs to worry

I’ve seen plenty of “Figma is dead” takes. I’ve been around long enough to distrust any “so-and-so is dead” pronouncement, and the lines people draw in the sand tend to be premature. Figma isn’t dead.

As someone who designs in code, I still can’t get past the fact that 99% of design jobs require Figma. It’s where teams manage their design tokens, run design reviews, and where the big companies keep their design system source of truth for multi-product systems. Claude Design doesn’t do any of that, and Anthropic isn’t pretending it does. The Canva partnership makes the positioning explicit. What Claude Design gives you in a few iterations is a really good draft, not a finished product. But it’s early, and the output is impressive.

The tools that should be watching closely are the ones sitting in the same lane: Stitch, Figma Make, Lovable, v0, bolt.new. The “describe a thing, get a working prototype” category. Claude Design isn’t at feature parity with any of them on depth yet. Lovable and Bolt generate full-stack apps with auth and a database. v0 has mature component-library integration. Stitch has a multi-screen canvas and voice.

But Claude Design does two things none of them do as well right now:

1. It reads your codebase to extract your design system. Point it at a repo, and every project after that uses your actual colors, typography, and components. Stitch has theme-level customization. Lovable, Bolt, and v0 can import a Figma file. Claude Design infers the system from production code.
2. It hands off directly to Claude Code. When a design is ready to build, Claude packages it into a bundle that Claude Code picks up with one instruction. That’s vertical integration between the design surface and the agent that writes the code.

The second one is the structural advantage. Stitch can export to AI Studio. Lovable generates its own backend. But my guess is that most developers actually shipping AI-assisted products right now are on Claude Code. A design tool that hands off to the coding agent those devs already trust is going to be hard to counter from the outside.

My first tries with it

A few experiments from the last week.

Generating a design system from a Figma project. I pointed Claude Design at a Figma file and had it extract a system I could apply to new screens for a prototype. It took a while and wasn’t production-ready (you’d want to pressure-test the token decisions), but it was close enough to have a real conversation about the design with the client.

Redesigning pitch deck slides with context-aware illustrations. A colleague has a pitch deck he’s been working on for an agency. I copied three slides and asked Claude Design to redesign them with animated illustrations tied to the topic of each slide. The illustrations actually corresponded to the content, which surprised me. What started as generic stock photos became modern illustrations that did a good job conveying abstract ideas.

Swiss grid variations from a single portfolio screen. I gave it the first screen from my portfolio and asked for layout variations based on different grids drawn from Josef Müller-Brockmann’s principles. Then out of curiosity I had it create illustrations to go with them. It treated the grid system as a design constraint, generated layouts that respected it, and made some genuinely interesting animated illustrations. For a designer who needs to explore, it delivered on the request: a lot of variations to spark ideas on something I’d been staring at for far too long.

A full DIY environment for konigi.com. I have a playground site, konigi.com, that I wanted to turn into a DIY-themed environment for fun. I generated a graphic in Nano Banana to set the scene, handed it to Claude Design, and asked it to build the experience around that graphic. What came back was closer to a site than a mockup. The kind of thing I’d normally spend a weekend wiring up.

None of these are shippable without my hands on them. All of them compressed what could’ve taken me a week of exploration into a few hours. That’s no exaggeration. I spent less than half an hour on the design system project and a few minutes on the pitch deck slides.

The last two projects, the portfolio and the playground page, ran a few hours each. After I had the portfolio screen and the playground package, I kept iterating and made them real on my server with Claude Code.

What this may foretell

Right now, Claude Design and Stitch are positioned as generation tools. You describe something, they produce something. The output keeps getting better, but it’s still a first draft that you refine in chat or export to a real design tool or to code for polish.

The scenario worth sitting with is what happens when the generative layer becomes the ideation surface for serious design work, and the professional tools have to rethink what they’re for.

Claude Design already gives you inspector-level control over individual elements. It holds design-system consistency at generation time, and it can code full application flows from the same canvas. Keep pulling that thread and the thing Figma does best, the fine-grained pushing and nudging of screen elements, starts to look like a subset of what a prompt-native tool can do. We’re not there yet. But the direction is hard to miss.

These tools are folding ideation, specification, and build onto one surface. Figma won its category by pulling design and collaboration into the browser. The next collapse pulls design and code into the agent itself.

When that happens, the designer’s real question stops being which tool to use. It becomes what you’re doing that the tool can’t. The answer, as I keep saying here, is design thinking: knowing what to build, finding the right problem, and making the calls a prompt can’t make for you.

Liz Miller, VP and principal analyst at Constellation Research, had this to say at Adobe Summit. “Just as master painters have different brushes they use for different things, you are never going to use Claude for design to create your finished masterpiece,” she told CMSWire. “You might use it and you might use OpenAI. You might even go and use a little Leonardo. You’re going to use a lot of different things to get you to your end point.”

She goes on to frame what Wall Street misses in its reaction. “While Wall Street is focused on outputs and how amazing those outputs are, Adobe continues to be focused on outcomes. And for an enterprise marketer, I’m going to bet on the outcome before I ever bet on the output.”

The output of Claude Design can be stunning and still not be the thing that turns an idea into a product that works for the people using it. The outcome is what matters. And the outcome depends on someone who knows what they’re trying to accomplish and can judge whether the generated work gets them closer.

The tools are getting very good at outputs, and Anthropic just made that harder to ignore. So the work moves up the stack, toward outcomes, problem definition, and the judgment calls a prompt can’t make. Knowing what to build, and whether what you got is any good, is still on you.

Where do we go from here?

Claude Design is a research preview. Features will change, limits will shift, and some of what I described above will break or get reworked before it stabilizes. That’s the nature of a Labs release.

But the shape of it is clear enough. A foundation-model company shipped a design product, wired it to its coding agent, and did it a month after its biggest competitor’s big release. Those are large moves, and they’ll leave a mark on the incumbent tools.

If you’re at Figma, Lovable, v0, bolt, or on the Stitch team, you already know this. If you’re a designer watching from the outside, the takeaway is simpler. The ground is moving under us faster than anyone expected a year ago. The designers who come out of this well are the ones treating these tools as collaborators for exploration, not threats to their craft.

The craft is still the craft. The tools are just getting a lot more interesting.