Claude Design Isn't Coming for Figma—It's After Something

Anthropic dropped Claude Design on a Friday afternoon. Not exactly the launch timing you'd expect for a product that's supposedly going to disrupt the design tool ecosystem. But then again, maybe the timing tells you something about what this actually is.

The release landed just after Mike Krieger—Anthropic's chief product officer—resigned from Figma's board. Markets read that as a declaration of war. The design tool comparison carousel started spinning immediately: Is this Figma? Is it Canva? Which billion-dollar company is Claude about to kill?

But after watching early adopters push the tool through its paces, I'm not convinced Anthropic is trying to replace any existing design tool. They're doing something narrower and weirder—and the confusion about what Claude Design actually is might be the most interesting part of the story.

Systems, Not Assets

Here's the split that's emerging from early usage: asset design versus systems design. Asset design is making a social post, a logo, a standalone graphic. Systems design is building a website, an application interface, a design system that governs dozens of components.

Canva excels at the first. Figma owns the second. Claude Design seems to be going after something in between—or maybe orthogonal to both.

The clearest signal about Anthropic's intent comes from who's actually using it. Not professional designers iterating in Figma. Not marketers cranking out Instagram posts. It's Claude Code power users who can't design but need to spec interfaces.

One early tester captured it: "I live in Claude code. The visual half has always been the break in my flow. Spec something in words, lose context, re-explain it to Figma, etc. Claude design is the missing half. Draft UI inside Claude with Opus 4.7 vision, iterate by talking to it, and the handoff to Claude code pulls your design systems into context automatically. Design to implementation in one conversation instead of three tools."

That's not a Figma replacement pitch. That's a workflow integration pitch for people who were never going to open Figma in the first place.

The Socratic Interface

The most interesting design choice in Claude Design isn't the sliders everyone's excited about—though they're genuinely clever, generating context-specific controls for spacing, color warmth, layout density per artifact. It's the Socratic questioning system.

When you prompt Claude Design, it doesn't just generate options. It interrogates your brief. What's the mobile app's main role? What's the number one flow to nail? How important is voice input?

But here's the subtle part: the questions themselves include multiple-choice options that function as design thinking prompts. The tool is teaching you to think about your design problem while extracting requirements. It's not a blank cursor demanding input—it's a conversation that shapes what you're trying to build.

Anyone who's used Claude Code or Cursor will recognize this pattern. The difference is it's reskinned for design decisions instead of technical architecture. And according to early testers, it's effective at getting non-designers to actually consider product questions they'd otherwise skip.

What It Actually Does Well

Early adoption has clustered around a few specific use cases. Marketing assets, especially email templates and social posts. Product website variations—not final production sites, but multiple directions to test. Wireframes and mockups for apps. Pitch decks.

Notice the pattern? These are all things that exist at the intersection of "needs to look decent" and "isn't the final version." Anthropic's own announcement leans into this: "realistic prototypes, product wireframes and mockups, design explorations."

That's different from how they talk about Claude Code, which they explicitly position as production-ready. The design tool is being pitched as exploration infrastructure, not final output. Whether that's strategic positioning or an honest assessment of current capabilities is an open question.

The technical approach reveals constraints. Claude Design uses SVGs and code to generate visuals, not a native image generator. That creates both limits and opportunities. One user generated "an Artemis 2 moon launch site in a few minutes" using just SVGs—impressive, but also fundamentally different from raster image generation. It's good at geometric, interactive, systematic visual content. Less good at photorealistic imagery or complex illustrations.

The Rate Limit Wall

If you talk to people actually using Claude Design, one complaint dominates everything else: rate limits. Not "the rate limits are annoying." More like "I hit my limit in 30 minutes and now I can't use it for a week."

Justine Moore from A16Z built a dating app interface, then immediately reported: "On another note, I hit rate limits on my max plan in under 30 minutes." Another user: "Oh, so Claude Design has its own usage limit outside of everything else and, of course, already hit it. So, now I can't use it until next Friday? Okay."

This isn't a minor UX friction. It's a fundamental constraint on who can actually use the tool and how. If you're a Claude Code power user trying to quickly spec an interface, burning through a week's allocation in one session makes the tool nearly unusable for iterative work.

The other major pain point: exports. PowerPoint conversions degrade quality. Canva imports throw errors. Screenshots work but aren't editable. HTML exports are clean. The export story suggests this tool was built primarily for handoff to Claude Code, not to existing design ecosystems.

The Disruption That Isn't

Here's what's interesting about the market response. When Krieger left Figma's board, people assumed Anthropic was going to war. But Canva's CEO, Melanie Perkins, is quoted on Claude Design's launch page. That's not the posture of someone who thinks they're being disrupted.

Maybe that's denial. Or maybe Canva actually understands something the markets don't: these tools serve different workflows. Claude Design isn't trying to replace your design tool. It's trying to eliminate the need to context-switch out of Claude when you need something visual.

The broader question is whether AI's transformation of coding sets a pattern for other knowledge work. We went from "vibe coding" as a weekend experiment to agentic coding as standard practice in about 18 months. Could design follow the same trajectory?

Maybe. But coding has properties that make it particularly AI-suitable: clear rules, objective correctness, easy iteration. Design is messier, more subjective, more human. The fact that Anthropic is positioning Claude Design as exploration tooling rather than production tooling might reflect that reality.

Or maybe in six months we'll look back on that positioning as a temporary hedge before they went all-in on replacing design tools entirely. The only certainty is that the design software landscape is less stable than it was last Friday.

—Dev Kapoor