On April 17, 2026, Anthropic Labs launched Claude Design — the most visually ambitious plugin to arrive in Claude Cowork since the original eleven shipped in January. It generates polished design systems, website prototypes, interactive sites, slide decks, and marketing one-pagers from a single prompt, running on top of the brand-new Claude Opus 4.7 vision model.
Three days earlier, Anthropic CPO Mike Krieger had quietly resigned from Figma's board. When Claude Design went live, Figma's stock slid roughly 5–7% in the same session. The signal was unmistakable: the first-draft layer of the design stack is now AI-native, and it lives inside Claude.
This is our running breakdown of what the plugin actually does, how it fits into the rest of the Cowork plugin ecosystem, and where the real tradeoffs are.
What Claude Design is (and is not)
Claude Design is not a thin wrapper around an image model. It is a full plugin that ships with its own slash commands, connectors, and a dedicated editing surface inside the Cowork app.
You can give it:
- A plain-language prompt ("build a pricing page for a B2B data product, blue/green palette, enterprise feel")
- An existing codebase, and it will infer your component library, type system, and brand
- A Figma export, PDF, or screenshot as visual reference
- A voice brief or meeting transcript, via the Productivity plugin
It returns editable artifacts — not static images. Everything renders on an in-canvas editor where you can:
- Comment directly on individual elements, the way you would in Figma
- Draw on mockups to indicate changes ("make this card bigger, remove this icon")
- Adjust fonts, spacing, and colors with live sliders instead of re-prompting
- Step backward at any point and regenerate a single component without blowing up the rest
Claude asks for approval at each stage. Nothing writes to your design files, your repo, or your deck unless you accept it.
What Claude Design replaces
This is where the Figma comparison gets sharp. Claude Design is aimed squarely at the first-draft layer of the design stack — the phase where most teams spend the most time and get the least credit.
| Today | With Claude Design | | --- | --- | | Designer spins up a Figma file, builds a component sketch, iterates for 2–3 days | Product lead describes the page, gets a structured prototype in minutes | | Marketing drags rectangles in Canva until a one-pager "looks right" | Marketing writes the message, Claude generates a branded layout | | Eng team hand-codes a landing page from a rough Figma frame | Claude Design exports standalone HTML or hands off to Claude Code | | Founder pays an agency for a pitch deck | Founder prompts a deck, edits in-canvas, exports to PPTX |
What it does not replace:
- High-fidelity production design systems maintained across dozens of squads
- Accessibility and interaction design work that needs a human in the loop
- The Design plugin's workflows — UX copy, a11y audits, design docs — which still pair cleanly with Claude Design and now run on the same Opus 4.7 model
Commands and workflows
Claude Design adds four primary slash commands to the Design plugin surface:
/design:prototype— Turn a brief or codebase into an interactive, multi-page site prototype/design:design-system— Generate tokens, typography, and a component library from a prompt or existing brand assets/design:slide-deck— Produce a pitch deck or internal presentation, exportable to PPTX or PDF/design:one-pager— Build a marketing or sales one-pager, exportable to PDF or published to WordPress via the new connector
Because it lives inside Cowork, it composes with the rest of your plugins:
- Marketing plugin → brand voice and campaign context flow into Claude Design automatically
- Product Management plugin → specs and user research become prototype inputs
- Sales plugin → deal briefs become pitch decks on demand
- Claude Code → hand off prototypes as production-ready React components (in research preview)
Export and handoff
Three native export targets ship on day one:
- PDF — decks, one-pagers, design docs
- PowerPoint (PPTX) — editable decks, including speaker notes generated from your brief
- Standalone HTML — fully working, responsive prototype in a single downloadable archive
Two handoff integrations shipped alongside it:
- Canva — one-click export of the full prototype or deck into a Canva workspace for final polish
- Claude Code — send a prototype into a Claude Code session and generate a production implementation against your existing component library
Handoff to Figma itself is listed on the public roadmap but is not live in the research preview.
Pricing and token economics
Claude Design does not require a separate subscription. It is included in existing Claude plans:
- Pro — included, subject to weekly token limits
- Max — higher weekly ceiling
- Team — shared team quota with admin controls
- Enterprise — custom limits, admin-managed deployment, audit logs
The honest caveat: Claude Design is token-heavy. One early tester built a full design system, a marketing website prototype, and a 60-second product video in a single afternoon and burned through more than half of a weekly Max quota. If you exceed your plan, pay-as-you-go rates apply — which can add up quickly for a team that treats the plugin as a daily driver.
For finance teams evaluating this: model it closer to "a retainer with an agency" than "a SaaS seat." The output quality and throughput justify the cost for first-draft work; they do not yet justify it for high-volume production design.
Why Figma's stock moved
Three reasons, ranked by how much they actually matter:
- Positioning. Figma's public pitch has leaned hard into AI-assisted design. Claude Design arrived from a better-funded competitor with a stronger frontier model and shipped on the same day as Opus 4.7.
- Distribution. Claude Cowork already sits on the desktops of millions of knowledge workers through existing plans. There is no separate signup, no seat negotiation, and no procurement cycle. That is a distribution advantage Figma cannot match overnight.
- The board signal. Mike Krieger's resignation from Figma's board three days before launch told the market that Anthropic had decided competition was the cleaner path.
None of this means Figma is going away. Professional design teams will keep living in Figma for production work, and Figma's own Claude Code plugin (/implement-design) is still one of the most installed plugins in the ecosystem. But the terms of the competition have changed.
How to enable Claude Design
- Open Claude Cowork on desktop and go to the Plugins tab
- Look for Claude Design under the "Anthropic Labs" section
- Click Install — it auto-enables the four
/designcommands - Optional: connect Canva and WordPress from the Integrations tab for one-click publishing
- Start with
/design:one-pagerif you want a five-minute demo of what the plugin can do
Or from the command line with Claude Code:
claude plugin marketplace add anthropics/labs-plugins
claude plugin install claude-design@labs-plugins
Bottom line
Claude Design is the first plugin where the plugin is bigger than the category. It is not another thin vertical add-on — it is a wedge into a mature, multibillion-dollar design tools market, delivered through the same Cowork surface that already handles your finance, legal, and sales work.
For individual operators and small teams, it collapses the "get something that looks designed" step from days to minutes. For enterprises, it adds a new lever: the first draft no longer requires a designer, a license to Figma, or a Canva seat per employee.
For Figma, it is a real competitor, in the market, today — powered by Opus 4.7, distributed through Cowork, and priced as part of a plan most of your team already has.
See the full plugin directory on the Plugins page, or continue with our February 2026 release notes for context on the rest of the ecosystem.