Killed By Claude Report
← HomeCurrent verdict
Assessment
Figma is in a real overlap zone, but not full extinction territory.
Claude now has concrete momentum in design, computer use, tool integrations, and especially design-to-code / code-to-design loops. That matters because those are exactly the adjacent workflows that make Figma more valuable.
But Anthropic's evidence pack mostly shows Claude working with Figma, not replacing the core Figma product. The threat is more subtle:
- Claude can compress parts of the design workflow into prompts and agents
- Claude can generate prototypes and implementations faster
- Claude can turn Figma from the main work surface into one node in a broader AI workflow
So yes, Figma is in the blast radius.
No, Claude does not yet look like a credible substitute for Figma's core multiplayer canvas, design system workflows, and entrenched enterprise collaboration.
Biggest historical hit
Claude Opus 4.6 is the clearest signal.
Anthropic explicitly cites that the model generates complex, interactive apps and prototypes in Figma Make, and even includes a quote from Figma's Chief Design Officer praising the model's ability to understand intent and co-create.
That is a direct warning shot: Anthropic is no longer just helping with writing or coding. It is credibly entering the creative prototyping and design-implementation loop that sits close to Figma's expansion surface.
What still protects them
Figma still has real defenses:
- The shared canvas moat
Real-time collaborative design is not just model output. It is a product surface, workflow habit, and team coordination layer.
- Design system gravity
Figma sits where components, tokens, layouts, review, iteration, and handoff already live.
- Enterprise distribution
The site signals deep penetration into large product organizations. Replacing that is much harder than demoing an agent.
- AI can increase Figma usage
Several announcements show Claude integrating with Figma, not displacing it. If Figma remains the canonical visual workspace, Claude may drive more activity into Figma rather than siphon it away.
The brutal truth: Figma is protected less by pure model defensibility and more by workflow centrality.
Signals
Why this is in the blast radius
This is the strongest direct overlap.
Anthropic says Opus 4.6 generates complex, interactive apps and prototypes in Figma Make. That pushes Claude into creative prototyping and product exploration, both adjacent to Figma's core workflow.
It does not mean Claude replaces Figma's collaborative canvas.
But it does mean Anthropic is helping perform higher-value design work that used to require more manual effort inside Figma.
Anthropic explicitly says Sonnet 4.6 improved across design, coding, computer use, and agent planning.
That combination overlaps with Figma's broader product-development story: brainstorm, design, prototype, handoff, build.
Still, this is platform capability overlap, not proof that Claude substitutes for Figma's main UI and collaboration product.
Anthropic says users can connect third-party tools like Figma directly within Claude.
That puts Claude in the orchestration seat and Figma in the tool layer underneath. If users increasingly initiate work from Claude, ownership of the workflow could drift upward toward Anthropic.
That is a meaningful strategic threat, even if Figma still provides the actual design environment.
Computer use lets Claude take multi-step actions inside live applications.
For Figma, that means Claude can potentially navigate design tools, manipulate files, move across product workflows, and automate repetitive design-adjacent tasks. That chips away at the manual interaction layer around Figma.
It still does not reproduce Figma's core multiplayer design surface by itself.
This is highly concrete.
Anthropic says Claude can read Figma mockups at the data level—component hierarchies, design tokens, auto-layout rules—and translate them into production-ready code.
That directly overlaps with handoff and implementation workflows where Figma has expanded its value. Claude is not replacing design creation here, but it is attacking the expensive bridge from design to build.
This update actually reinforces Figma as the destination canvas.
Claude can generate a working prototype in code and send it into Figma to explore versions. That makes Claude a creation engine, but Figma remains the visual workspace for review, iteration, and collaboration.
So this is overlap, yes—but it is also evidence that Figma remains infrastructure in the workflow rather than being cut out.