Figma vs Claude Design

Agent ops

1. ai-native userAn agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them

   weight 2 · round to Figma
   Figma✓fullprobed9/10

   Figma's official MCP server explicitly documents write-capable tools ("Write to the canvas: Create and modify native Figma content directly from your MCP client", "enabling agents to write native Figma content back to the canvas"), plus the Plugin API supports full read/write access to create and modify file contents, and the REST API includes create/update/delete endpoints (e.g., Variables API). This is corroborated by multiple first-party docs and a dedicated probe confirming the MCP server's existence. Missing for 10: no independent hands-on report specifically validating write-via-MCP in production use.

   • [claimed-docs] “Write to the canvas: Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “enabling agents to write native Figma content back to the canvas”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”
   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “The Plugin API supports both **read** and **write** access to Figma's editors, allowing developers to view, create, and modify the contents …”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”

   proof ↗⚑ flag

   Claude Design~partialprobed4/10

   There's no documented first-party write API or MCP server for Claude Design itself (OpenAPI probe returned 404s), but Claude Code slash-commands (/design, /design-sync) and handoff bundles let an agent programmatically create/modify designs, and one community report describes a working MCP flow pushing Claude Design output into PenPot with reusable components. Missing for 10: official documented MCP server/API surface for Claude Design, broader independent corroboration of agent-driven write access beyond a single anecdote.

   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”

   proof ↗⚑ flag

2. ai-native userAn agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface

   weight 2 · round to Figma
   Figma~partialprobed6/10

   Figma's docs show agents can extract design data and generate code from frames via the MCP server and REST API (figma-docs-39, figma-docs-40, figma-docs-59, figma-docs-49), and the REST API is documented as a programmatic surface for pulling objects/layers. However, the evidence pack never explicitly documents an image/screenshot rendering or production-format export endpoint (e.g., PNG/SVG/PDF render API) for agent use — most citations focus on writing to canvas, code generation, and diagram creation rather than visual export. Missing for 10: explicit documentation of an image-rendering/export endpoint or MCP tool for screenshots/production image formats, and independent/hands-on confirmation of such export working via the programmatic surface.

   • [claimed-docs] “Select a Figma frame and turn it into code. Great for product teams building new flows or iterating on app features.”
   • [claimed-docs] “Pull in variables, components, and layout data directly into your IDE. This is especially useful for design systems and component-based work…”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”
   • [claimed-docs] “view and extract any objects or layers, and their properties from files”
   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”

   proof ↗⚑ flag

   Claude Design~partialprobed5/10

   Docs confirm export to PPTX/PDF/HTML and a Claude Code handoff bundle triggered via /design-sync, and community reports an MCP-based flow (into PenPot) suggesting some programmatic surface exists, but there is no documented API/SDK for rendering or exporting designs and the openapi probe returned 404s, indicating no formal machine-callable spec. missing for 10: documented API/SDK for export, evidence of screenshot/image export via a callable interface, corroborated OpenAPI or MCP server documentation.

   • [claimed-docs] “Export to PPTX, PDF, or HTML, share an org-scoped link, hand off to Claude Code, or send to the apps you already use daily.”
   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”

   proof ↗⚑ flag

3. ai-native userMy coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design

   weight 3 · round to Figma
   Figma✓fullprobed9/10

   Figma ships a first-party MCP server (local and remote) with documented tools for extracting variables, components, layout data, generating code from frames, and writing back to canvas, plus REST API endpoints for variables, layers, and Code Connect for component-to-code mapping — directly matching the story. Evidence spans official docs, GitHub repo, and a probe confirming the live MCP server endpoint. Missing for 10: independent hands-on developer report specifically validating MCP-based design-to-code extraction (community evidence covers general Figma-to-code pain points but not the MCP server itself).

   • [claimed-docs] “Extract design context: Pull in variables, components, and layout data directly into your IDE.”
   • [claimed-docs] “Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “Select a Figma frame and turn it into code. Great for product teams building new flows or iterating on app features.”
   • [claimed-docs] “Pull in variables, components, and layout data directly into your IDE. This is especially useful for design systems and component-based work…”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”
   • [claimed-docs] “`get_variable_defs` extracts the **variables and styles** used in your selection (color, spacing, typography, etc).”
   • [claimed-docs] “enabling agents to write native Figma content back to the canvas”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [claimed-docs] “Sync design system source of truth to and from Figma”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”
   • [claimed-docs] “Figma's remote MCP server makes it possible to connect directly to your Figma files without needing to install Figma's desktop app.”

   proof ↗⚑ flag

   Claude Design~partialcommunity5/10

   Claude Design ships explicit hand-off paths for coding agents — /design-sync to pull the design system into Claude Code, packaged handoff bundles, and import from GitHub/codebase/component libraries — which functionally lets an agent implement designs with real context. However, the mechanism is documented as slash-command/bundle integration rather than an explicit MCP server or general API exposing frames, variables, screenshots, and component mappings; the one community mention of MCP (comm-7) describes Claude Design consuming an external tool's MCP (PenPot), not exposing its own for coding agents to pull context. missing for 10: first-party documentation of an MCP server or API surface for frames/variables/screenshots/component mappings, and independent verification that agents (not just Claude Code) can pull that structured context.

   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”
   • [claimed-docs] “Import from GitHub, design files, or your local codebase so Claude can build with your real components.”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [community] “I have been using Claude Design + Claude Code, and results have been excellent. The handoff skill in Claude Design is pretty solid.”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Figma
   Figma✓fullprobed8/10

   A probe confirms a live llms.txt file at https://developers.figma.com/llms.txt returning HTTP 200 with a structured description of Figma's developer platform docs, directly enabling an agent to be pointed at it. Missing for 10: independent/community confirmation of an agent successfully consuming the file, and no evidence of additional agent-oriented doc formats (e.g., openapi.json, which 404s).

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.figma.com/llms.txt # Figma Developer Documentation > Documentation for building on Figma's d…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.figma.com/openapi.json, https://developers.figma.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Claude Design✓fullprobed7/10

   Probes confirm llms.txt is live (HTTP 200) at the Claude support domain and that Claude Design's own docs page is available in agent-friendly markdown form (docs-md probe), meaning an agent could be pointed at these resources to learn the product. Missing for 10: explicit vendor documentation describing llms.txt as an intended agent-consumption channel, and community/hands-on confirmation that an agent actually used llms.txt to complete a task with Claude Design.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.claude.com/llms.txt # Claude Help Center > Search for answers or browse by topic ## English #…”
   • [probe] “PROBE docs-md: HTTP 200 at https://support.claude.com/en/articles/14604416-get-started-with-claude-design.md # Get started with Claude Desig…”

   proof ↗⚑ flag

2. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Claude Design
   Figma—none0/10

   All MCP-related evidence describes Figma exposing its own MCP server for external clients (e.g., IDEs, coding agents) to consume Figma's tools — the opposite direction of this story, which asks whether Figma itself can plug in and use external MCP servers' tools. No evidence shows Figma's AI/agent features acting as an MCP client capable of consuming third-party MCP servers.

   ⚑ flag

   Claude Design~partialcommunity3/10

   Only a single ambiguous community mention notes 'Claude Design into PenPot via its MCP,' suggesting some MCP-based integration exists, and docs reference pulling data from tools like Salesforce/QuickBooks/HubSpot without specifying MCP as the mechanism. There is no official documentation confirming users can plug arbitrary MCP servers into Claude Design to expose their tools. Missing for 10: first-party docs on MCP server support, clarity on directionality (client vs server), and broader independent confirmation beyond one ambiguous forum comment.

   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [claimed-docs] “Turn this proposal into a one-pager a prospect will want to open. Pull their details from Salesforce and export it as a PDF.”
   • [claimed-docs] “Dig into your numbers in Intuit QuickBooks, plan a promotion to get sales up, generate branded assets in Canva, and get your next campaign s…”

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round to Figma
   Figma~partialprobed5/10

   Figma does ship an official CLI (Code Connect CLI, documented at the quickstart guide) which is used to sync design system components in code with Figma and keep MCP-generated code consistent with the codebase — supporting agentic/CI-style workflows. However, the evidence pack gives no detail on CLI command surface, scripting for AI agents, or independent hands-on validation beyond its existence. Missing for 10: detailed CLI usage docs for AI-native/agentic workflows, examples of CLI use in automated/agent pipelines, independent corroboration of the CLI's capabilities.

   • [probe] “official CLI documented at https://developers.figma.com/docs/code-connect/quickstart-guide/”
   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma. When using Code Connect, Figma…”
   • [claimed-docs] “Code Connect keeps your generated code consistent with your codebase.”

   proof ↗⚑ flag

   Claude Design—none0/10

   Evidence shows Claude Design integrates with Claude Code via slash commands (/design-sync, /design) and handoff bundles, but this is Claude Code's CLI, not an official CLI shipped by Claude Design itself; no standalone CLI for Claude Design is documented.

   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”

   proof ↗⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round to Figma
   Figma✓fullprobed9/10

   Figma publishes a well-documented REST API (with OpenAPI spec on GitHub), webhooks, Plugin API, and an official MCP server enabling agentic control of designs, code generation, and diagrams—giving AI-native users multiple documented, programmatic ways to drive the product. Missing for 10: a discoverable live OpenAPI/swagger endpoint on the docs domain itself (probe found 404s) and more independent hands-on corroboration of API robustness beyond vendor docs.

   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [claimed-docs] “Leverage the power of our REST API to bring Figma into your external tools and products.”
   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”
   • [claimed-docs] “Write to the canvas: Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.figma.com/openapi.json, https://developers.figma.com/swagger.json, https://develo…”
   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”

   proof ↗⚑ flag

   Claude Design—none0/10

   Evidence pack shows only end-user product docs (import/export, design generation, handoff to Claude Code) and no documented public API; a direct probe for OpenAPI/swagger specs at claude.com/support returned 404s, and no REST/SDK API for Claude Design is mentioned anywhere.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to Figma
   Figma✓fullprobed8/10

   Figma provides an official REST API with OpenAPI spec and TypeScript types (figma-docs-46), a Plugin/Widget API (figma-docs-8, figma-docs-32), Code Connect SDK/CLI on GitHub (figma-gh-1, figma-gh-2, figma-docs-60), and an official MCP server for AI-native workflows (figma-probe-3, figma-docs-1). These are well-documented, first-party SDKs/APIs explicitly built for programmatic and AI-agent integration. missing for 10: no independent hands-on developer corroboration of SDK reliability/completeness, and probe found no discoverable openapi.json at the expected well-known endpoints despite a spec repo existing.

   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”
   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “The Plugin API supports both **read** and **write** access to Figma's editors, allowing developers to view, create, and modify the contents …”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”
   • [claimed-docs] “Write to the canvas: Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “This guide helps you connect your React (or React Native) components with Figma components using Code Connect.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.figma.com/openapi.json, https://developers.figma.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   Claude Design—none0/10

   Claude Design's evidence pack shows only end-user product docs (mockups, prototypes, handoff, exports) and community discussion of MCP integration with third-party tools like PenPot, but no mention of an official SDK for building against Claude Design itself. A direct probe for API/OpenAPI specs returned 404s, indicating no public developer SDK is documented.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Claude Design
   Figma!disputedcontradicted5/10

   Figma documents an AI agent that generates design directions, diagrams, images, and searches files, and touts 'AI agents work in the same space with shared context' (figma-docs-17, figma-docs-34, figma-docs-51), which matches the story's intent of AI-generated insights/suggestions from the user's own design data. However, hands-on community feedback specifically contradicts this: 'the AI tools in FigJam are really bad and often broken' (figma-comm-8), while another user reports success summarizing notes into slides (figma-comm-9), giving mixed real-world evidence rather than a clean full delivery. Missing for 10: independent benchmarks or broader corroboration of AI insight quality/reliability across Figma (not just FigJam), and clearer documentation of insight-generation (vs. content-generation) use cases.

   • [claimed-docs] “Use the Figma agent to generate new design directions, create diagrams, edit images, search your files, and more.”
   • [claimed-docs] “Compare multiple directions side by side and dig into the details with your whole team. Anyone can edit designs and riff with the agent to r…”
   • [claimed-docs] “Teammates and AI agents work in the same space with shared context. Generate new design directions, refine, and align—together.”
   • [community] “Figma itself is great. Figjam is okay. Slides was literally made because they realized customers were using Figma for presentations, but the…”
   • [community] “With the integration of AI, people are using Figma for more than just design - a friend used it to input notes/data and have its AI summariz…”

   proof ↗⚑ flag

   Claude Design~partialclaimed5/10

   Claude Design can pull in external data (Salesforce, QuickBooks, GitHub) and use it to generate on-brand designs, proposals, or campaign plans, which is a limited form of data-driven suggestion, but this is framed around design generation rather than analytical insight delivery, and no evidence shows dedicated 'insights/suggestions' features from uploaded datasets. missing for 10: dedicated data-analysis/insight generation UI, independent corroboration that it surfaces analytical insights (not just design outputs) from imported data.

   • [claimed-docs] “Turn this proposal into a one-pager a prospect will want to open. Pull their details from Salesforce and export it as a PDF.”
   • [claimed-docs] “Dig into your numbers in Intuit QuickBooks, plan a promotion to get sales up, generate branded assets in Canva, and get your next campaign s…”
   • [claimed-docs] “Import from GitHub, design files, or your local codebase so Claude can build with your real components.”
   • [claimed-docs] “Import from your codebase, a web capture, or DOCX, PPTX, and XLSX files.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Figma
   Figma~partialclaimed5/10

   Figma exposes webhooks and REST API that let external systems react to events (comments, version changes) and CI/CD integrations, which supports background automation infrastructure, but there is no evidence of a native, autonomous scheduled agent or background-running automation within Figma itself — plugins/widgets require user invocation or live session context. Missing for 10: evidence of a built-in scheduler/autonomous agent execution mode, and independent confirmation that webhook-driven automations run fully unattended without additional third-party glue.

   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files. For example: a collaborator comments on a file, or you add a new version…”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files.”
   • [claimed-docs] “useful for needs like CI/CD implementations, logging, creating user-agnostic webhooks, and other tasks that you normally wouldn't want gated…”
   • [claimed-docs] “Integrate Figma directly with continuous integration (CI) systems.”
   • [claimed-docs] “Create and manage [webhooks](/docs/rest-api/webhooks-endpoints/)”
   • [claimed-docs] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”
   • [claimed-docs] “Unlike plugins that run for a specific person, everyone can see and interact with the same widget.”

   proof ↗⚑ flag

   Claude Design—none0/10

   Claude Design is a conversational/interactive design tool for generating mockups, prototypes, and handoffs; nothing in the evidence describes scheduled tasks, triggers, or autonomous background runs — all workflows are synchronous and user-initiated via chat or explicit commands.

   ⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Claude Design
   Figma!disputedcontradicted5/10

   Figma ships a built-in AI agent (Figma AI/Make) that can generate designs, diagrams, edit images, search files, and collaborate with teammates in real time (figma-docs-17, figma-docs-34, figma-docs-51), which matches the story of delegating tasks to an in-product assistant. However, a hands-on community report explicitly states the AI tools (in FigJam) are 'really bad and often broken' (figma-comm-8), directly contradicting the vendor's polished framing of reliable delegation. Missing for 10: independent corroboration that the assistant reliably completes delegated tasks, and detail on task scope/limits beyond marketing copy.

   • [claimed-docs] “Use the Figma agent to generate new design directions, create diagrams, edit images, search your files, and more.”
   • [claimed-docs] “Compare multiple directions side by side and dig into the details with your whole team. Anyone can edit designs and riff with the agent to r…”
   • [claimed-docs] “Teammates and AI agents work in the same space with shared context. Generate new design directions, refine, and align—together.”
   • [community] “Figma itself is great. Figjam is okay. Slides was literally made because they realized customers were using Figma for presentations, but the…”
   • [community] “With the integration of AI, people are using Figma for more than just design - a friend used it to input notes/data and have its AI summariz…”

   proof ↗⚑ flag

   Claude Design✓fullcommunity8/10

   Claude Design is built around delegating design tasks directly to Claude within the product—describing a visual, refining through conversation/sliders, generating variations, and packaging handoffs are all done by the embedded Claude assistant, and this is corroborated by hands-on community reports of building shippable pages and using the handoff skill successfully. missing for 10: independent quality benchmarking of how much genuine agentic reasoning vs templated generation occurs, and some community reports note underwhelming or 'boring' outputs suggesting delegation quality varies.

   • [claimed-docs] “Describe a visual and Claude builds a first version, on brand.”
   • [claimed-docs] “Refine, share, or hand off to the tools you use. You're the designer, start to finish.”
   • [claimed-docs] “you refine through conversation, inline comments, direct edits, or custom sliders (made by Claude) until it's right”
   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [community] “Used Claude Design to build the landing page for my side project over the weekend. Got something shippable in a few hours. It's great for 80…”
   • [community] “I have been using Claude Design + Claude Code, and results have been excellent. The handoff skill in Claude Design is pretty solid.”
   • [community] “I tested it yesterday. Kinda impressive, but also design output is pretty boring.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Claude Design
   Figma~partialcommunity5/10

   Figma ships a first-party AI agent (natural-language design generation, image editing, file search, diagram creation, and Figma Make for prompt-to-prototype) letting users operate parts of the product conversationally, plus an MCP server enabling agent-driven natural-language control from IDEs. However, community feedback specifically calls the FigJam AI tools 'really bad and often broken,' and there's no independent corroboration that the core Figma AI agent reliably handles broad natural-language operation across the whole product surface (only marketing copy). Missing for 10: independent hands-on validation of the Figma AI agent's reliability, evidence of NL command coverage beyond generation/diagramming/search, and resolution of the FigJam AI quality complaints.

   • [claimed-docs] “Use the Figma agent to generate new design directions, create diagrams, edit images, search your files, and more.”
   • [claimed-docs] “Compare multiple directions side by side and dig into the details with your whole team. Anyone can edit designs and riff with the agent to r…”
   • [claimed-docs] “From there, share a PRD and build with your existing design context intact.”
   • [claimed-docs] “Teammates and AI agents work in the same space with shared context. Generate new design directions, refine, and align—together.”
   • [claimed-docs] “Prototype. Polish. Ship. Your ideas get real in Figma Make.”
   • [community] “Figma itself is great. Figjam is okay. Slides was literally made because they realized customers were using Figma for presentations, but the…”
   • [community] “With the integration of AI, people are using Figma for more than just design - a friend used it to input notes/data and have its AI summariz…”

   proof ↗⚑ flag

   Claude Design✓fullcommunity8/10

   Claude Design's entire interaction model is natural-language: users 'describe a visual and Claude builds a first version,' refine 'through conversation, inline comments,' and use conversational handoffs like /design and /design-sync — with real-world use (landing pages, PenPot flows) confirming this works in practice, though output quality and robustness vary across users. Missing for 10: consistent quality/benchmarks across users and no independent rigor testing beyond anecdotal HN reports.

   • [claimed-docs] “Describe a visual and Claude builds a first version, on brand.”
   • [claimed-docs] “you refine through conversation, inline comments, direct edits, or custom sliders (made by Claude) until it's right”
   • [claimed-docs] “Now you can use Claude Design from inside any conversation with Claude.”
   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [community] “Used Claude Design to build the landing page for my side project over the weekend. Got something shippable in a few hours. It's great for 80…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [community] “I tested it yesterday. Kinda impressive, but also design output is pretty boring.”

   proof ↗⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Figma
   Figma✓fullprobed8/10

   Figma publishes an OpenAPI specification and TypeScript types for its REST API in a public GitHub repo (figma-docs-46), which is machine-readable and downloadable, directly satisfying the story. Probe evidence shows the spec isn't hosted at conventional /openapi.json paths on the docs site (figma-probe-2), so discoverability is slightly less standard. Missing for 10: a directly hosted spec endpoint on developers.figma.com and independent confirmation of spec completeness/versioning.

   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.figma.com/openapi.json, https://developers.figma.com/swagger.json, https://develo…”
   • [claimed-docs] “Leverage the power of our REST API to bring Figma into your external tools and products.”

   proof ↗⚑ flag

   Claude Design—none0/10

   Claude Design is a design/prototyping product with no evidence of a public API, and the direct probe for OpenAPI/swagger endpoints returned 404 on all candidate paths, with no other documentation mentioning a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”

   proof ↗⚑ flag

2. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Claude Design
   Figma—none0/10

   No evidence of a sandbox/staging environment or test mode that isolates AI-native testing from production Figma data; all MCP/API/plugin docs describe operating directly on real files and production content. missing for 10: any mention of sandbox environments, test/staging Figma instances, mock data, or non-production testing modes for AI agent workflows.

   ⚑ flag

   Claude Design~partialclaimed5/10

   Claude Design's core workflow is prototyping (mockups, interactive prototypes) that are explicitly separate from production code — 'no PRs, no code review' before user-testing — which implies a sandbox-like separation from shipped/production systems. However, there is no explicit mention of a dedicated sandbox environment, test data isolation, or protection of 'production data' in a technical/backend sense; the framing is about design/code review gating rather than data safety. missing for 10: explicit sandbox/staging environment terminology, guarantees about not touching production data or backend systems, and independent confirmation of this isolation in practice.

   • [claimed-docs] “Turn a static mockup into a shareable, interactive prototype you can test with real people. No PRs, no code review.”
   • [claimed-docs] “Designers can turn static mockups into easily-shareable interactive prototypes to gather feedback and user-test, without code review or PRs.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”

   proof ↗⚑ flag

Ai

1. designerBuilt-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor

   weight 1 · round to Figma
   Figma~partialcommunity5/10

   Figma's own site claims an in-editor AI agent that can 'generate new design directions, create diagrams, edit images, search your files, and more' (figma-docs-17, figma-docs-34), which covers some asset-chore functions like image editing and diagram generation, but the evidence never mentions background removal, content-aware fill, or copy/microcopy suggestions specifically. A community report also flags that Figma's AI tools (in FigJam) are 'really bad and often broken' (figma-comm-8), undermining confidence in reliability. missing for 10: explicit documentation of background removal, content-aware fill, and copy-suggestion features, plus independent hands-on validation that these AI asset tools work reliably.

   • [claimed-docs] “Use the Figma agent to generate new design directions, create diagrams, edit images, search your files, and more.”
   • [claimed-docs] “Compare multiple directions side by side and dig into the details with your whole team. Anyone can edit designs and riff with the agent to r…”
   • [claimed-docs] “Purchase AI credits for your whole team to share. Enable pay-as-you-go for flexibility or subscribe to save.”
   • [community] “Figma itself is great. Figjam is okay. Slides was literally made because they realized customers were using Figma for presentations, but the…”

   proof ↗⚑ flag

   Claude Design~partialclaimed3/10

   Claude Design can generate full visual designs from a text prompt and offers layout/color adjustment sliders (claude-design-docs-13, claude-design-docs-9), which loosely maps to 'image generation' and some asset tuning, but there is no evidence of dedicated background-removal, content-aware fill, or copy-suggestion tools built into the editor. missing for 10: background removal tool, content-aware fill/inpainting, in-editor copy/headline suggestion feature.

   • [claimed-docs] “Describe a visual and Claude builds a first version, on brand.”
   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [claimed-docs] “you refine through conversation, inline comments, direct edits, or custom sliders (made by Claude) until it's right”

   proof ↗⚑ flag

2. designerGenerate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces

   weight 2 · round drawn
   Figma~partialcommunity6/10

   Figma's own docs describe a genuine prompt-to-design capability: the 'Figma agent' can 'generate new design directions, create diagrams, edit images' from prompts, users can 'riff with the agent to refine' designs, and 'Figma Make' turns ideas into working prototypes (figma-docs-17, figma-docs-34, figma-docs-51, figma-docs-56, figma-docs-43). However, this is all vendor-sourced documentation with no independent hands-on report confirming quality of first drafts/mockups, and one community comment specifically calls Figma's AI tools 'really bad and often broken' (figma-comm-8), tempering confidence in real-world reliability. Missing for 10: independent/hands-on verification of output quality for full mockups, and resolution of the community report of broken AI features.

   • [claimed-docs] “Use the Figma agent to generate new design directions, create diagrams, edit images, search your files, and more.”
   • [claimed-docs] “Compare multiple directions side by side and dig into the details with your whole team. Anyone can edit designs and riff with the agent to r…”
   • [claimed-docs] “Teammates and AI agents work in the same space with shared context. Generate new design directions, refine, and align—together.”
   • [claimed-docs] “Prototype. Polish. Ship. Your ideas get real in Figma Make.”
   • [claimed-docs] “From there, share a PRD and build with your existing design context intact.”
   • [community] “Figma itself is great. Figjam is okay. Slides was literally made because they realized customers were using Figma for presentations, but the…”

   proof ↗⚑ flag

   Claude Design~partialcommunity6/10

   First-party docs and community reports confirm Claude Design generates first drafts, multiple directions, layouts, and mockups from natural-language prompts with editing/refinement controls (docs-13,20,9,21; comm-6,7,16), and users describe shippable landing pages and solid handoff. However hands-on community feedback also reports underwhelming, 'boring', or 'useless' results for some prompts and generic upload errors (comm-3,9,10,8), showing real quality variance rather than a uniformly reliable draft-to-mockup pipeline. Missing for 10: consistent independent benchmarking of output quality across prompt types, and resolution of reported failure cases (large file uploads, simple prompts underwhelming).

   • [claimed-docs] “Describe a visual and Claude builds a first version, on brand.”
   • [claimed-docs] “Designers can quickly create a wide range of directions to explor”
   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [claimed-docs] “you refine through conversation, inline comments, direct edits, or custom sliders (made by Claude) until it's right”
   • [community] “Used Claude Design to build the landing page for my side project over the weekend. Got something shippable in a few hours. It's great for 80…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”
   • [community] “I have been using Claude Design + Claude Code, and results have been excellent. The handoff skill in Claude Design is pretty solid.”
   • [community] “After having high expectations from watching the intro, the actual result of a simple prompt 'Bear on a bicycle' is very underwhelming.”
   • [community] “I tested it yesterday. Kinda impressive, but also design output is pretty boring.”
   • [community] “I've tried it. It's useless.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Figma
   Figma~partialcommunity5/10

   Figma's REST/Variables APIs, Plugin API, and webhooks let developers script operations across many objects/files (e.g., variables CRUD, library analytics across all files, plugin read/write over full documents), which supports bulk automation, but there's no native first-class 'bulk operation' feature in the product itself — community evidence shows users still rely on third-party bulk-export plugins for basic tasks like exporting many icons at once, indicating manual/plugin workarounds rather than built-in bulk tooling. missing for 10: dedicated bulk-edit/bulk-apply UI or MCP tool for acting on many layers/files simultaneously, independent verification that plugin/REST scripting reliably scales to large batches, and first-party documentation explicitly describing bulk operations as a supported workflow.

   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [claimed-docs] “Get summary information about how many instances of a library's components exist across all files.”
   • [claimed-docs] “Get time series data about what actions your users have performed with your library's components on a week-by-week basis.”
   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “The Plugin API supports both **read** and **write** access to Figma's editors, allowing developers to view, create, and modify the contents …”
   • [community] “Grabbing icons as individual SVGs is probably what takes me the longest going from design to code. I have to click on each asset, name it pr…”
   • [community] “Right Click the icon > Copy/Paste as > Copy as SVG. We use that and just paste it into the codebase. Also used a bulk export plugin that aut…”

   proof ↗⚑ flag

   Claude Design~partialclaimed4/10

   Claude Design supports generating multiple design directions at once (claude-design-docs-2) and applying a design system consistently 'to every project automatically' (claude-design-docs-3), which suggests some batch-like automation, but there's no evidence of true bulk operations across many items (e.g., batch editing dozens of files/assets, bulk export/import at scale, or programmatic multi-item processing). missing for 10: evidence of bulk/batch processing across many discrete items (not just generating variants), bulk edit/export APIs, scale limits, and independent confirmation of multi-item automation workflows.

   • [claimed-docs] “Generate a dozen directions in minutes, then narrow down in your primary tool.”
   • [claimed-docs] “Claude can also apply your team's design system to every project automatically, so the output is consistent with the rest of your company's …”

   proof ↗⚑ flag

2. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Figma
   Figma~partialclaimed4/10

   Figma documents general file version history (view/revert past versions) which would cover changes made via MCP/plugins since they write to the same canvas, but there is no automation-specific review or rollback mechanism (e.g., audit log of agent/plugin actions, diff-and-approve flow, or per-automation rollback) documented anywhere in the MCP, plugin, or REST API docs. Missing for 10: automation-specific change review/approval workflow, dedicated rollback for AI-agent or plugin actions, and any audit trail distinguishing automated vs manual edits.

   • [claimed-docs] “View a file's version history”
   • [claimed-docs] “Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “enabling agents to write native Figma content back to the canvas”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”

   proof ↗⚑ flag

   Claude Design—none0/10

   The evidence pack describes Claude Design's prototyping, design-system sync, and handoff features, but contains no mention of version history, review workflows, or rollback capability for any automations or design iterations it produces. Community comments even note lock-out of prior work after unsubscribing, with no rollback/versioning remedy mentioned.

   ⚑ flag

Collaboration

1. product managerComment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email

   weight 2 · round to Figma
   Figma✓fullclaimed6/10

   Figma's core design docs confirm in-file commenting and multiplayer feedback ("share feedback with comments... in one shared space") and webhooks reference collaborators commenting on files, matching the core of the story, but the pack never explicitly documents @mention or thread-resolution UI. Missing for 10: explicit documentation of @mentioning teammates and resolving comment threads, plus independent hands-on confirmation beyond marketing copy.

   • [claimed-docs] “Work together in multiplayer files, share feedback with comments, and talk to your teammates with cursor chat in one shared space.”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files. For example: a collaborator comments on a file, or you add a new version…”

   proof ↗⚑ flag

   Claude Design~partialclaimed3/10

   Evidence shows collaborative editing (grant edit access, group conversation) and 'inline comments' as a refinement mechanism, but there's no documented @mention-teammates feature or thread-resolution workflow that would replace email-based review. Missing for 10: explicit @mention of teammates, comment thread resolution/status tracking, and any hands-on confirmation that commenting works as a review tool rather than just a chat refinement input.

   • [claimed-docs] “grant edit access so colleagues can modify the design and chat with Claude together in a group conversation”
   • [claimed-docs] “you refine through conversation, inline comments, direct edits, or custom sliders (made by Claude) until it's right”

   proof ↗⚑ flag

2. designerMy whole team can edit the same file simultaneously with live cursors and instant sync

   weight 3 · round to Figma
   Figma✓fullclaimed8/10

   Figma's docs directly describe multiplayer files with shared editing, cursor chat, and real-time collaboration ('Work together in multiplayer files... talk to your teammates with cursor chat in one shared space'; 'together in real-time and in one place'), matching the core story. Missing for 10: independent/hands-on verification of live-cursor sync at scale and no detail on conflict resolution or performance limits under heavy concurrent editing.

   • [claimed-docs] “Work together in multiplayer files, share feedback with comments, and talk to your teammates with cursor chat in one shared space.”
   • [claimed-docs] “Figma allows designers to create and prototype their digital experiences - together in real-time and in one place”
   • [claimed-docs] “Made for the big picture. Perfect down to every pixel.”

   proof ↗⚑ flag

   Claude Design~partialclaimed4/10

   Docs mention granting edit access so colleagues can modify a design and chat with Claude in a group conversation, implying some shared editing, but there is no evidence of live cursors, simultaneous multi-user editing, or instant real-time sync mechanics typical of multiplayer design tools. Missing for 10: explicit live-cursor/presence indicators, real-time simultaneous editing demonstration, and independent confirmation of true multiplayer sync.

   • [claimed-docs] “grant edit access so colleagues can modify the design and chat with Claude together in a group conversation”

   proof ↗⚑ flag

Design systems

1. designerManage design tokens or variables — colors, spacing, typography — with modes or themes applied across designs

   weight 2 · round to Figma
   Figma✓fullclaimed8/10

   Figma has native Variables with modes/themes for color, spacing, and typography, a dedicated Variables REST API for querying/creating/updating/deleting tokens and syncing design-system source of truth, and MCP tooling (get_variable_defs) that extracts variables and styles across selections; docs explicitly recommend using Figma variables for tokens across spacing, color, radius, and typography. Missing for 10: independent hands-on validation of multi-mode theming workflows and more detail on cross-file/library token publishing at scale.

   • [claimed-docs] “Sync design system source of truth to and from Figma”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [claimed-docs] “`get_variable_defs` extracts the **variables and styles** used in your selection (color, spacing, typography, etc).”
   • [claimed-docs] “Use Figma variables for tokens. Apply variables for spacing, color, radius, and typography.”
   • [claimed-docs] “Pull in variables, components, and layout data directly into your IDE. This is especially useful for design systems and component-based work…”

   proof ↗⚑ flag

   Claude Design~partialcommunity3/10

   Claude Design can 'apply your team's design system to every project automatically' and offers sliders to tune spacing/color, and one community report describes it building 'reusable PenPot components and design system tokens' via an MCP export flow — but there's no first-party evidence of native token/variable definitions with mode/theme switching (light/dark, brand variants) inside Claude Design itself. missing for 10: explicit token/variable editor, multi-mode/theme support, first-party documentation of applying themes across multiple designs.

   • [claimed-docs] “Claude can also apply your team's design system to every project automatically, so the output is consistent with the rest of your company's …”
   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”

   proof ↗⚑ flag

2. designerBuild reusable components with variants and per-instance overrides that stay linked to their source

   weight 3 · round to Figma
   Figma~partialclaimed3/10

   The evidence pack only points to a help-center article titled 'Guide to components in Figma' without any quoted content describing variants, per-instance overrides, or override-linking behavior; no other citation addresses this specific design-systems capability. Missing for 10: explicit documentation or examples of variant properties, instance override behavior, and how overrides remain linked to (and reset from) the main component.

   • [claimed-docs] “Guide to components in Figma”
   • [claimed-docs] “Translate designs into code”

   proof ↗⚑ flag

   Claude Design—none0/10

   Claude Design is described as a prompt-driven design/prototyping tool that can 'apply your team's design system' and import components, but there is no evidence of a structured component system with defined variants and per-instance overrides that stay linked to a master source, as in tools like Figma. The one related community mention (comm-7) is about exporting to PenPot's component system, not a native capability of Claude Design itself.

   • [claimed-docs] “Claude can also apply your team's design system to every project automatically, so the output is consistent with the rest of your company's …”
   • [claimed-docs] “Import from GitHub, design files, or your local codebase so Claude can build with your real components.”
   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”

   proof ↗⚑ flag

3. designerShared libraries publish components and styles across files and projects, with controlled updates when the source changes

   weight 2 · round to Figma
   Figma~partialclaimed5/10

   Docs confirm centralized library/asset publishing across teams and departments (figma-docs-37, figma-docs-12) and a components guide (figma-docs-72), plus library usage analytics across files (figma-docs-55, figma-docs-75), but there is no explicit documentation in the pack of the update-notification/accept-update workflow when a library source component changes. missing for 10: explicit doc on component update propagation/notification workflow, independent/hands-on confirmation of controlled update behavior.

   • [claimed-docs] “Want to centralize assets, libraries, and workflows across departments”
   • [claimed-docs] “Publish resources across teams”
   • [claimed-docs] “Guide to components in Figma”
   • [claimed-docs] “Get summary information about how many instances of a library's components exist across all files.”
   • [claimed-docs] “Get time series data about what actions your users have performed with your library's components on a week-by-week basis.”
   • [claimed-docs] “Unlimited files and projects for a single team”

   proof ↗⚑ flag

   Claude Design~partialclaimed3/10

   Claude Design can apply a team's design system automatically across projects and sync design-system context via '/design-sync' from Claude Code, suggesting some cross-project consistency, but there is no evidence of a true shared-library mechanism (publishing reusable components/styles with versioned, controlled updates propagating when a source library changes) as in dedicated design tools. Missing for 10: library publishing workflow, update/versioning notifications when source components change, and independent confirmation of cross-project sync behavior.

   • [claimed-docs] “Claude can also apply your team's design system to every project automatically, so the output is consistent with the rest of your company's …”
   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”

   proof ↗⚑ flag

Handoff

1. developerDesigns map to production code — component-to-code mappings or direct design-to-code output I can actually ship

   weight 2 · round drawn
   Figma~partialcommunity7/10

   Figma ships strong first-party dev-handoff tooling: Code Connect maps design system components directly to real production code snippets in Dev Mode (figma-gh-1, figma-gh-2, figma-docs-60), and the MCP server can generate code from selected frames, extract variables/component context, and even build into production (figma-docs-2, figma-docs-39, figma-docs-25, figma-docs-35). However, community evidence shows real friction shipping that code as-is — devs complain about receiving absolute-position CSS instead of usable layout code and needing manual/plugin workarounds for asset export (figma-comm-1, figma-comm-2, figma-comm-3), and advanced Dev Mode/MCP access is gated behind a paid tier (figma-comm-4, figma-docs-23). Missing for 10: independent hands-on validation that MCP/Code-Connect output is shippable without manual cleanup at scale, and confirmation that core code-mapping isn't paywalled behind Dev Mode license.

   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [claimed-docs] “This guide helps you connect your React (or React Native) components with Figma components using Code Connect.”
   • [claimed-docs] “Select a Figma frame and turn it into code. Great for product teams building new flows or iterating on app features.”
   • [claimed-docs] “Code Connect keeps your generated code consistent with your codebase.”
   • [claimed-docs] “Turn your design into a code-backed prototype, or build it into production with Figma’s MCP server.”
   • [community] “I hate when figma just always gives me CSS for absolute positioning. Is there any way around that?”
   • [community] “Grabbing icons as individual SVGs is probably what takes me the longest going from design to code. I have to click on each asset, name it pr…”
   • [community] “Right Click the icon > Copy/Paste as > Copy as SVG. We use that and just paste it into the codebase. Also used a bulk export plugin that aut…”
   • [community] “2023: available for all users. 2024: separate license for Dev Mode. I guess Figma trying to get more paying customers... feel a bit Adobe vi…”
   • [claimed-docs] “Advanced Dev Mode inspection and MCP Server”

   proof ↗⚑ flag

   Claude Design~partialcommunity7/10

   Docs describe concrete design-to-code handoff: importing real components from GitHub/codebase, syncing design systems via /design-sync, and packaging a 'handoff bundle' passed to Claude Code with one instruction (claude-design-docs-5,6,7,8). Community corroborates this works well ('handoff skill in Claude Design is pretty solid', 'Got something shippable in a few hours') but also flags that the generated code is often unmaintainable ('write-once, read-never' code) and animation/export sanitization bugs, showing real shippability caveats. Missing for 10: independent verification of true component-to-code mapping fidelity (not just handoff bundling) and resolution of maintainability/code-quality concerns raised by users.

   • [claimed-docs] “Import from GitHub, design files, or your local codebase so Claude can build with your real components.”
   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”
   • [community] “I have been using Claude Design + Claude Code, and results have been excellent. The handoff skill in Claude Design is pretty solid.”
   • [community] “It makes absolutely beautiful designs, stunningly so, but the actual code is not something a human could ever maintain. Write-once, read-nev…”
   • [community] “Used Claude Design to build the landing page for my side project over the weekend. Got something shippable in a few hours. It's great for 80…”

   proof ↗⚑ flag

2. developerInspect any layer and get measurements, styles, assets, and code snippets (CSS/iOS/Android) without an editor seat

   weight 3 · round to Figma
   Figma~partialcommunity5/10

   Figma's Dev Mode (figma-docs-64, figma-docs-23) and MCP tools like get_variable_defs (figma-docs-68) support extracting styles, variables, and code snippets, and Code Connect (figma-gh-1/3) provides true-to-production code snippets, with community confirmation of CSS export workflows (figma-comm-1/2/3). However, the evidence never explicitly confirms iOS/Android snippet generation, precise measurement tooling, or that Dev Mode access requires only a lower-cost seat rather than a full editor seat—figma-docs-23 even ties 'Advanced Dev Mode inspection' to a paid plan tier. missing for 10: explicit iOS/Android code snippet evidence, explicit seat-tier confirmation (dev seat vs editor seat), measurement/spec inspection detail beyond CSS.

   • [claimed-docs] “Development and design, connected at every step.”
   • [claimed-docs] “Advanced Dev Mode inspection and MCP Server”
   • [claimed-docs] “`get_variable_defs` extracts the **variables and styles** used in your selection (color, spacing, typography, etc).”
   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma. When using Code Connect, Figma…”
   • [community] “I hate when figma just always gives me CSS for absolute positioning. Is there any way around that?”
   • [community] “Grabbing icons as individual SVGs is probably what takes me the longest going from design to code. I have to click on each asset, name it pr…”
   • [community] “2023: available for all users. 2024: separate license for Dev Mode. I guess Figma trying to get more paying customers... feel a bit Adobe vi…”

   proof ↗⚑ flag

   Claude Design—none0/10

   Evidence shows Claude Design can export handoff bundles and code (HTML/CSS/JS) to Claude Code or as PPTX/PDF/HTML, but there is no mention of a layer-level 'inspect' mode giving measurements, styles, assets, and platform-specific (CSS/iOS/Android) code snippets for viewers without an editor seat — the axis is applicable to a design/dev-handoff tool but unevidenced here.

   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”
   • [claimed-docs] “Export to PPTX, PDF, or HTML, share an org-scoped link, hand off to Claude Code, or send to the apps you already use daily.”
   • [community] “It makes absolutely beautiful designs, stunningly so, but the actual code is not something a human could ever maintain. Write-once, read-nev…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Figma
   Figma~partialprobed5/10

   Figma exposes several APIs (REST API for reading objects/variables/webhooks, Plugin API for read/write of file contents, MCP server for writing to canvas and generating code/diagrams) that cover a large slice of UI functionality, but no evidence shows full parity — e.g. REST API is largely read/webhook-oriented, Plugin API requires running inside the editor UI rather than headless automation, and there's no documented API for things like commenting, team/project management, or prototyping interactions equivalent to the UI. missing for 10: comprehensive REST/plugin coverage of comments, prototyping settings and team administration, evidence of headless parity without plugin UI context, and independent confirmation that API-driven workflows match UI capability 1:1.

   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “provides tools for reading designs out of Figma, writing designs into Figma, connecting designs to your codebase, and building generative pl…”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [claimed-docs] “The Plugin API supports both **read** and **write** access to Figma's editors, allowing developers to view, create, and modify the contents …”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”

   proof ↗⚑ flag

   Claude Design—none0/10

   No evidence of a Claude Design API; the only API-related probe found openapi.json/swagger.json endpoints all returning 404, and no docs mention programmatic access to Design's prototyping, handoff, or editing features. All capabilities (prototyping, handoff, design-system sync) are described only as UI/Claude Code slash-command workflows.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.claude.com/openapi.json, https://support.claude.com/swagger.json, https://support.cl…”
   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “Now you can use Claude Design from inside any conversation with Claude.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Claude Design
   Figma!disputedcontradicted3/10

   Figma's REST API and Plugin API let you extract objects, layers, properties, and variables (figma-docs-7, figma-docs-26, figma-docs-49, figma-docs-62), suggesting some data portability, but this falls short of a genuine 'export all your data in open formats and leave' capability — designs remain in Figma's proprietary .fig format with no full-fidelity open-format export. A hands-on community report explicitly contradicts openness: 'your full fidelity work is locked up in a proprietary format' and you can't keep a fully up-to-date local copy without constant manual export (figma-comm-7). Missing for 10: an actual bulk/full-fidelity open-format export or documented data-portability/exit path, and no contradiction from independent sources.

   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [claimed-docs] “view and extract any objects or layers, and their properties from files, get usage data, or listen for events with webhooks”
   • [claimed-docs] “view and extract any objects or layers, and their properties from files”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [community] “Not only is it weird that with Figma you don't get to keep a local file if you don't constantly export to keep your local copy up to date - …”

   proof ↗⚑ flag

   Claude Design!disputedcontradicted4/10

   Docs confirm export to open-ish formats (PPTX, PDF, HTML) and that designs are HTML/CSS/JS editable by any tool, suggesting an open-format export path. However, community reports document a concrete failure: users lost access to their entire design history/projects after unsubscribing, effectively blocking 'leaving' with their data, which Anthropic staff acknowledged as a bug needing a fix rather than confirming it works as intended. Missing for 10: a documented, reliable full-data export mechanism (all chats, assets, code) confirmed to work post-cancellation, and independent verification that the promised fix was shipped.

   • [claimed-docs] “Export to PPTX, PDF, or HTML, share an org-scoped link, hand off to Claude Code, or send to the apps you already use daily.”
   • [community] “Dont use Claude Design, lost access to my projects after unsubscribing.”
   • [community] “It's pretty outrageous to lock out all your history just for canceling the subscription.”
   • [community] “If you export your data, all your Claude Design chats are in a design_chats directory along with the code, even if your account currently ha…”
   • [community] “Hi there, Thariq from the Claude team here. Sorry this is happening, we'll fix it ASAP. Claude's designs are HTML/CSS/JS that any editor can…”

   proof ↗⚑ flag

Plugins

1. designerExtend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more

   weight 2 · round to Figma
   Figma✓fullcommunity7/10

   Figma's Plugin API and Widget API docs explicitly support a broad plugin ecosystem for reading/writing files, building custom UI, and automating workflows 'from documentation to communication' (figma-docs-8, figma-docs-18, figma-docs-36, figma-docs-65), and independent hands-on community evidence confirms designers actually use third-party plugins (e.g., bulk SVG export/autonaming) in real workflows (figma-comm-3). Private plugin support for internal tooling is also documented (figma-docs-9). Missing for 10: explicit mention of a named 'Community/marketplace' browsing experience, plugin counts/scale, or concrete examples of accessibility-checker/data-filler plugins specifically.

   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “Create private plugins and widgets to keep internal information and data safe.”
   • [claimed-docs] “Users and organizations take advantage of plugins to customize their experience and create more efficient workflows.”
   • [claimed-docs] “Automate tasks, add new functionality, and improve your workflow with plugins for everything from documentation to communication.”
   • [claimed-docs] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”
   • [claimed-docs] “Unlike plugins that run for a specific person, everyone can see and interact with the same widget.”
   • [community] “Right Click the icon > Copy/Paste as > Copy as SVG. We use that and just paste it into the codebase. Also used a bulk export plugin that aut…”

   proof ↗⚑ flag

   Claude Design—none0/10

   No evidence of a plugin marketplace or extensibility ecosystem for Claude Design (icons, data fillers, accessibility checkers, etc.); the only related mention is a single user connecting Claude Design to PenPot via MCP, which is a one-off integration, not a documented plugin/marketplace system.

   • [community] “Claude Design into PenPot via its MCP was a really neat flow, with correct prompts it even built out reusable PenPot components and design s…”

   proof ↗⚑ flag

Pricing

1. product managerPublished plan pricing makes seat types, tiers, and AI-feature gating clear before procurement

   weight 1 · round to Figma
   Figma~partialclaimed5/10

   Figma's public pricing page fragments show tier-gated features (e.g., 'Advanced Dev Mode inspection and MCP Server', 'Centralized admin tools', 'Publish resources across teams', 'Unlimited files and projects for a single team') and separate AI credit purchasing/allocation controls, indicating some AI-feature and tier gating is documented pre-purchase. However, the evidence pack lacks a full seat-type/tier comparison table, explicit per-seat pricing, or a clear breakdown of which AI features are included vs. add-on across each named plan (Starter/Professional/Organization/Enterprise), so the story is only partially supported. Missing for 10: explicit seat-type definitions, full tier-by-tier feature/price matrix, and clear enumeration of which AI capabilities are gated at each tier.

   • [claimed-docs] “Publish resources across teams”
   • [claimed-docs] “Centralized admin tools”
   • [claimed-docs] “Advanced Dev Mode inspection and MCP Server”
   • [claimed-docs] “Purchase AI credits for your whole team to share. Enable pay-as-you-go for flexibility or subscribe to save.”
   • [claimed-docs] “You have full control and visibility over how credits are allocated and used across your team.”
   • [claimed-docs] “Want to centralize assets, libraries, and workflows across departments”
   • [claimed-docs] “Unlimited files and projects for a single team”

   proof ↗⚑ flag

   Claude Design—none0/10

   The evidence pack shows product features, an enterprise admin toggle, and usage-bar mentions, but contains no documentation of seat types, pricing tiers, or explicit AI-feature gating tables for procurement decisions.

   ⚑ flag

2. designerThe free tier supports real design work — usable editor and collaboration without a paid seat

   weight 2 · round drawn
   Figma—none0/10

   The evidence pack describes general Figma design/collaboration/prototyping capabilities (figma-docs-14, figma-docs-15, figma-docs-16) but nothing ties these specifically to the free tier vs. paid seats, and no pricing page excerpt enumerates what the free plan includes. One community note (figma-comm-4) even flags a trend of moving features (Dev Mode) behind paid licenses, but this doesn't confirm or deny free-tier usability for core design work either way.

   ⚑ flag

   Claude Design—none0/10

   The evidence pack contains no information about a free tier for Claude Design, its editor capabilities without payment, or collaboration limits for non-paying users. In fact, community reports indicate access is tied to an active subscription and is revoked upon cancellation (comm-11, comm-12, comm-13), which cuts against the idea of a functional free tier, but there's no direct claim or denial of a free tier's design capabilities to judge against.

   • [community] “Dont use Claude Design, lost access to my projects after unsubscribing.”
   • [community] “It's pretty outrageous to lock out all your history just for canceling the subscription.”
   • [community] “If you export your data, all your Claude Design chats are in a design_chats directory along with the code, even if your account currently ha…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Figma—none0/10

   No evidence in the pack addresses data residency, regional storage options, or data localization controls for Figma; all evidence concerns design tools, MCP server capabilities, plugins, and collaboration features. Missing for 10: any mention of region selection, data residency commitments, or storage location controls.

   ⚑ flag

   Claude Design—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage controls for Claude Design; only Enterprise admin enable/disable toggle is discussed, not residency.

   • [claimed-docs] “For Enterprise organizations, Claude Design is off by default. Admins can enable it in Organization settings.”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Figma—none0/10

   No evidence pack items address AI training data opt-out or data usage controls for AI model training; nothing about privacy settings, data processing agreements, or opt-out toggles is mentioned. This axis applies to Figma (a data-handling SaaS platform where AI training opt-out is a plausible policy), but no supporting evidence exists.

   ⚑ flag

   Claude Design—none0/10

   No evidence in this pack addresses training-data opt-out or privacy controls for Claude Design; the pack covers only product features, enterprise admin toggles, and unrelated community feedback.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Figma—none0/10

   No evidence pack items address data retention policies, deletion controls, or data lifecycle management for AI features; the pack covers MCP tooling, plugins, REST API, and collaboration features but nothing about retention/deletion settings for AI-native users. missing for 10: data retention policy documentation, deletion controls/APIs, AI data handling/opt-out settings, any admin controls for purging AI-processed data.

   ⚑ flag

   Claude Design—none0/10

   The evidence pack contains no documentation of user-controlled data retention or deletion settings for Claude Design; instead, community reports describe users being locked out of their design projects entirely after canceling a subscription, with Anthropic acknowledging the issue and promising a fix, rather than any dashboard/API for retention policy or deletion control.

   • [community] “Dont use Claude Design, lost access to my projects after unsubscribing.”
   • [community] “It's pretty outrageous to lock out all your history just for canceling the subscription.”
   • [community] “If you export your data, all your Claude Design chats are in a design_chats directory along with the code, even if your account currently ha…”
   • [community] “Hi there, Thariq from the Claude team here. Sorry this is happening, we'll fix it ASAP. Claude's designs are HTML/CSS/JS that any editor can…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Figma—none0/10

   No evidence pack items address telemetry/usage-tracking opt-out settings or privacy controls of that kind; the evidence covers MCP server features, plugins, REST API, and admin/SCIM tools but nothing about disabling analytics or tracking for AI-native workflows.

   ⚑ flag

   Claude Design—none0/10

   No evidence in the pack discusses telemetry/usage-tracking opt-out settings for Claude Design; the only related item confirms a separate usage bar, not a privacy control. Missing for 10: any documentation or setting for opting out of telemetry/usage tracking.

   ⚑ flag

1. designerPrototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product

   weight 1 · round to Figma
   Figma~partialclaimed5/10

   Figma's docs confirm high-fidelity, interactive, no-code prototyping and dedicated animation/motion tooling ([figma-docs-16],[figma-docs-33],[figma-docs-28]), supporting the 'feel like the real product' goal, but the evidence pack never explicitly documents prototyping-specific conditional logic, variables-driven interactions, or scroll-triggered effects (these are general Figma features not detailed here). Missing for 10: explicit documentation of conditions/variables used within prototype interactions, scroll-effect prototyping, and independent hands-on validation of these advanced behaviors.

   • [claimed-docs] “Figma's prototyping tools make it easy to build and share high-fidelity, no-code, interactive prototypes.”
   • [claimed-docs] “Figma’s prototyping tools make it easy to build and share high-fidelity, no-code, interactive prototypes.”
   • [claimed-docs] “Create precise animations, build out reusable motion systems, and ship dev-ready animations.”

   proof ↗⚑ flag

   Claude Design~partialcommunity4/10

   Docs claim Claude Design produces 'interactive prototypes' that can be user-tested and 'look like the real product' via web capture, and community evidence confirms animated SVGs can be built, but with real friction (animations stripped by default sanitization, requiring workarounds). There is no evidence addressing prototype conditions/variables or scroll-based effects specifically. missing for 10: explicit support for state-based/conditional logic in prototypes, scroll-triggered effects, and clean first-party documentation of animation between screens/states without the SVG export bug.

   • [claimed-docs] “Turn a static mockup into a shareable, interactive prototype you can test with real people. No PRs, no code review.”
   • [claimed-docs] “Designers can turn static mockups into easily-shareable interactive prototypes to gather feedback and user-test, without code review or PRs.”
   • [claimed-docs] “You can also use the web capture tool to grab elements directly from your website so prototypes look like the real product.”
   • [community] “I've been using Claude Design to make animated SVGs. You have to ask it to first come up with a robust way to define the geometry and then a…”
   • [community] “Whatever tool prepares the SVG for export in Claude Design will strip animations as part of a sanitizing process; you have to export as a di…”

   proof ↗⚑ flag

2. designerWire screens into clickable prototypes with triggers, transitions, and overlays — no code required

   weight 2 · round to Figma
   Figma✓fullcommunity9/10

   Figma's docs explicitly market native, no-code prototyping tools ('high-fidelity, no-code, interactive prototypes'), which per general product knowledge and the docs pages cover triggers, transitions, and overlays as core interaction-design features, corroborated by community praise for Figma's rapid feature growth in design/prototyping workflows. missing for 10: no explicit line-item mention of 'triggers/transitions/overlays' terminology or independent hands-on walkthrough of building a specific prototype flow.

   • [claimed-docs] “Figma's prototyping tools make it easy to build and share high-fidelity, no-code, interactive prototypes.”
   • [claimed-docs] “Figma’s prototyping tools make it easy to build and share high-fidelity, no-code, interactive prototypes.”
   • [claimed-docs] “With best-in-class layout tools, type tools, and more, you have full control over how you design.”
   • [community] “Over the last five years Illustrator has added no useful new features and XD has wandered with no clear direction. Meanwhile Figma has been …”

   proof ↗⚑ flag

   Claude Design~partialcommunity4/10

   Docs confirm Claude Design turns static mockups into shareable, testable interactive prototypes without code (claude-design-docs-1, claude-design-docs-18), which covers the no-code prototyping goal, but there is no evidence of specific multi-screen wiring primitives like triggers, transitions, or overlays that a designer would use in traditional prototyping tools. Community feedback (claude-design-comm-6, claude-design-comm-9) discusses general design output quality but not this specific screen-linking mechanic. Missing for 10: explicit support for defining triggers/transitions/overlays between distinct screens, and any hands-on confirmation that multi-screen flows can be wired together.

   • [claimed-docs] “Turn a static mockup into a shareable, interactive prototype you can test with real people. No PRs, no code review.”
   • [claimed-docs] “Designers can turn static mockups into easily-shareable interactive prototypes to gather feedback and user-test, without code review or PRs.”
   • [community] “Used Claude Design to build the landing page for my side project over the weekend. Got something shippable in a few hours. It's great for 80…”
   • [community] “I tested it yesterday. Kinda impressive, but also design output is pretty boring.”

   proof ↗⚑ flag

Canvas

1. designerFrames can behave responsively — auto layout, constraints, and grids resize designs the way real UIs flex

   weight 2 · round to Figma
   Figma~partialclaimed2/10

   Evidence pack lacks any explicit mention of Figma's auto layout, constraints, or grid systems; the closest is a vague marketing line about 'best-in-class layout tools' which doesn't name the specific responsive-design mechanics the story describes. missing for 10: explicit docs on auto layout resizing behavior, constraint pinning, layout grids, and any hands-on corroboration of responsive frame behavior.

   • [claimed-docs] “With best-in-class layout tools, type tools, and more, you have full control over how you design.”

   proof ↗⚑ flag

   Claude Design—none0/10

   The evidence pack describes Claude Design as a prompt-driven generator that outputs HTML/CSS/JS mockups and prototypes, with only generic 'rich layout controls' to drag/resize/align elements (claude-design-docs-9) — there is no mention of Figma-style frames, auto layout, constraints, or grid systems that adapt responsively. Community feedback even notes the generated code is not maintainable/structured (claude-design-comm-15), suggesting it isn't built on a constraint-based vector layout engine. Missing for 10: any documentation of frames, auto-layout, constraint-based resizing, or grid systems enabling responsive behavior.

   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [community] “It makes absolutely beautiful designs, stunningly so, but the actual code is not something a human could ever maintain. Write-once, read-nev…”

   proof ↗⚑ flag

2. designerI get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work

   weight 3 · round to Figma
   Figma~partialclaimed4/10

   Figma's marketing copy claims 'best-in-class layout tools, type tools' and pixel-precise control (figma-docs-15, figma-docs-63), which implies strong vector design capability, but the evidence pack contains no specific documentation of pen/path tools, boolean operations, or precise alignment guides — these are core to the story but unevidenced here. Community comments focus on SVG export and Dev Mode licensing, not vector editing quality itself. Missing for 10: explicit docs/screenshots of pen tool and path editing, boolean operation (union/subtract/intersect) documentation, alignment/snapping tool documentation, and independent hands-on corroboration of vector editing precision.

   • [claimed-docs] “With best-in-class layout tools, type tools, and more, you have full control over how you design.”
   • [claimed-docs] “Made for the big picture. Perfect down to every pixel.”
   • [claimed-docs] “Create precise animations, build out reusable motion systems, and ship dev-ready animations.”

   proof ↗⚑ flag

   Claude Design—none0/10

   Claude Design is a prompt-driven design/prototyping generator with only basic layout controls (drag, resize, align, sliders for spacing/color) — there is no evidence of pen/path vector editing, boolean path operations, or precision alignment tooling akin to professional vector editors. Community feedback even notes the underlying output is HTML/CSS/JS, not vector paths, and code is not maintainable, reinforcing it's not a vector design tool.

   • [claimed-docs] “use the adjustment sliders Claude creates to tune spacing and color. Use rich layout controls for quick visual and aesthetic shifts, includi…”
   • [community] “It makes absolutely beautiful designs, stunningly so, but the actual code is not something a human could ever maintain. Write-once, read-nev…”
   • [community] “I've been using Claude Design to make animated SVGs. You have to ask it to first come up with a robust way to define the geometry and then a…”
   • [community] “Whatever tool prepares the SVG for export in Claude Design will strip animations as part of a sanitizing process; you have to export as a di…”

   proof ↗⚑ flag

Files

1. designerExport production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices

   weight 2 · round to Figma
   Figma~partialcommunity4/10

   Community evidence confirms Figma supports exporting assets like SVGs (e.g., 'Copy as SVG', bulk export plugins) but only as a workaround with friction, not a documented first-party export panel with per-layer presets, scales, and slices. missing for 10: first-party docs describing the native Export panel, per-layer export presets, multiple-scale exports (1x/2x/3x), PDF export, and slice tool; independent confirmation these work smoothly without third-party plugins.

   • [community] “Grabbing icons as individual SVGs is probably what takes me the longest going from design to code. I have to click on each asset, name it pr…”
   • [community] “Right Click the icon > Copy/Paste as > Copy as SVG. We use that and just paste it into the codebase. Also used a bulk export plugin that aut…”

   proof ↗⚑ flag

   Claude Design~partialcommunity3/10

   Claude Design documents export to PPTX, PDF, and HTML, and community evidence confirms SVG export is possible (though it strips animations unless renamed), showing some baseline export capability exists. However, there is no evidence anywhere in the pack of PNG export, per-layer export presets, scale multipliers, or slice/asset regions — the core professional export controls the story asks about are entirely unevidenced. missing for 10: PNG export, per-layer export presets, scale export options, slice/asset export regions, any evidence of production-asset export workflows beyond whole-document PDF/PPTX/HTML.

   • [claimed-docs] “Export to PPTX, PDF, or HTML, share an org-scoped link, hand off to Claude Code, or send to the apps you already use daily.”
   • [community] “I've been using Claude Design to make animated SVGs. You have to ask it to first come up with a robust way to define the geometry and then a…”
   • [community] “Whatever tool prepares the SVG for export in Claude Design will strip animations as part of a sanitizing process; you have to export as a di…”

   proof ↗⚑ flag

2. developerThe file format is open or documented, so my designs stay portable and toolable outside the vendor's editor

   weight 1 · round to Claude Design
   Figma—none0/10

   Figma's native .fig file format itself is not published as an open or documented spec; the evidence pack offers only programmatic access surfaces (REST API, Plugin API, MCP server) rather than an open file-format specification, and community evidence explicitly states design work is 'locked up in a proprietary format' with no offline/local file portability without constant export.

   • [community] “Not only is it weird that with Figma you don't get to keep a local file if you don't constantly export to keep your local copy up to date - …”
   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [claimed-docs] “Leverage the power of our REST API to bring Figma into your external tools and products.”

   proof ↗⚑ flag

   Claude Design~partialcommunity6/10

   Claude Design outputs are HTML/CSS/JS and can be exported to PPTX, PDF, or HTML (claude-design-docs-8), and an Anthropic team member explicitly confirmed 'Claude's designs are HTML/CSS/JS that any editor can handle' (claude-design-comm-14), supporting portability outside the vendor's editor. However, there was a real-world incident where users temporarily lost access to their design history/code after unsubscribing (claude-design-comm-11, claude-design-comm-12) before the fix, and community members note the generated code is hard for humans to maintain (claude-design-comm-15), undercutting practical toolability. missing for 10: a stable, always-available raw export/download path independent of subscription status, and clearer documentation of the underlying file format/spec beyond ad-hoc HTML/CSS/JS.

   • [claimed-docs] “Export to PPTX, PDF, or HTML, share an org-scoped link, hand off to Claude Code, or send to the apps you already use daily.”
   • [community] “Dont use Claude Design, lost access to my projects after unsubscribing.”
   • [community] “It's pretty outrageous to lock out all your history just for canceling the subscription.”
   • [community] “If you export your data, all your Claude Design chats are in a design_chats directory along with the code, even if your account currently ha…”
   • [community] “Hi there, Thariq from the Claude team here. Sorry this is happening, we'll fix it ASAP. Claude's designs are HTML/CSS/JS that any editor can…”
   • [community] “It makes absolutely beautiful designs, stunningly so, but the actual code is not something a human could ever maintain. Write-once, read-nev…”

   proof ↗⚑ flag

3. designerFull version history lets me name milestones, compare, and restore any earlier state of a file

   weight 2 · round to Figma
   Figma~partialclaimed3/10

   Only one citation confirms version history viewing exists (figma-docs-44), but the evidence pack contains no detail on naming milestones, comparing versions, or restoring earlier states. missing for 10: documentation on naming/labeling versions, comparing diffs between versions, restoring a file to an earlier state, and any independent/hands-on corroboration of these capabilities.

   • [claimed-docs] “View a file's version history”

   proof ↗⚑ flag

   Claude Design—none0/10

   No evidence describes named milestones, version comparison, or restore-to-earlier-state functionality in Claude Design; community discussion only mentions losing access to 'history' after unsubscribing, not a versioning/milestone/compare/restore feature.

   • [community] “Dont use Claude Design, lost access to my projects after unsubscribing.”
   • [community] “It's pretty outrageous to lock out all your history just for canceling the subscription.”
   • [community] “If you export your data, all your Claude Design chats are in a design_chats directory along with the code, even if your account currently ha…”

   proof ↗⚑ flag