Sketch 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 Sketch
   Sketch✓fullclaimed8/10

   Sketch documents multiple write-capable programmatic surfaces: an official JavaScript Plugin API for creating/modifying designs, sketchtool CLI, sketch:// URL scheme for workflow integration, and explicit MCP support letting any MCP-compatible AI client connect to Sketch, including AI features that build out whole frames/pages from a repo. This goes beyond read-only inspection (which is the separate developer-handoff feature) into actual design creation/modification via agent tooling. Missing for 10: independent hands-on verification that MCP tools can actually write/modify designs (evidence is vendor-only), and no detailed spec of exposed MCP tool actions.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”

   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 Sketch
   Sketch✓fullprobed7/10

   Sketch documents `sketchtool`, a command-line tool explicitly for creating/exporting assets programmatically, plus an official JavaScript plugin API and 'integrate into workflows and server applications' language, giving agents a documented surface to render/export designs; MCP support further lets AI clients drive Sketch. Missing for 10: independent/hands-on verification of sketchtool's export formats and no explicit mention of headless/server rendering outside macOS, and no OpenAPI/REST surface was found (probe 404s).

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   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 Sketch
   Sketch✓fullclaimed7/10

   Sketch's own docs explicitly describe an MCP server integration ('Connect any MCP-compatible AI client you like to Sketch') that lets an AI client pull frames and recreate text styles, colors, UI components and pages, then build them out in code with 1:1 visual fidelity — directly matching the story's design-context-to-implementation workflow. Missing for 10: independent/hands-on verification of the MCP server actually working, explicit mention of pulling 'variables' or raw screenshots through the API, and any third-party corroboration beyond vendor marketing pages.

   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   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 Sketch
   Sketch✓fullprobed8/10

   Sketch actually publishes an llms.txt file that returns HTTP 200 and serves a structured docs index for agent consumption (getting-started, prototyping, developer-handoff, workspace docs), confirmed by both docs listing and a runtime probe. Missing for 10: no evidence of broader agent-oriented markdown mirrors (the /docs/.md probe 404s) or an OpenAPI/machine-readable schema beyond llms.txt.

   • [claimed-docs] “Learn how Single Sign-On (SSO) and SCIM provisioning work in Sketch, and find step-by-step guides to get set up.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.sketch.com/llms.txt # Sketch ## Docs - [Getting started](https://www.sketch.com/docs/getting-start…”
   • [probe] “PROBE runtime (recorded 2026-09-07): https://www.sketch.com/llms.txt served a full docs index ('# Sketch') for agent consumption, covering g…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.sketch.com/docs/.md”

   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
   Sketch—none0/10

   Evidence only shows Sketch acting as an MCP *server* that external AI clients (e.g. Claude, Cursor) can connect to and use Sketch's own tools (sketch-docs-18, sketch-docs-34) — the reverse of the story, which asks whether Sketch itself can plug in external MCP servers to consume their tools. No documentation or community evidence indicates Sketch can act as an MCP client consuming third-party tool servers.

   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   proof ↗⚑ 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 Sketch
   Sketch~partialclaimed6/10

   Sketch ships an official CLI, `sketchtool`, documented for asset creation and integration into workflows/server applications on any platform, which agentic/AI tools could invoke. However, there's no evidence this CLI is positioned or extended for AI-native agent workflows specifically (no mention of AI agents using sketchtool, no JSON/agent-friendly output specs, and MCP support is a separate non-CLI integration). Missing for 10: agent-oriented CLI documentation, examples of AI/agent usage of sketchtool, independent hands-on confirmation of its use in automated pipelines.

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Use the Sketch Plugin Manager `skpm` to publish a new plugin or an update of an existing one.”

   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 Sketch
   Sketch✓fullprobed7/10

   Sketch documents an official vanilla JavaScript plugin API 'fully supported between releases', a CLI (`sketchtool`), a `sketch://` URL scheme for workflow/server integration, and explicit MCP support so any MCP-compatible AI client can connect and drive Sketch — directly matching the AI-native/agentic story. However there's no REST/HTTP API or OpenAPI spec (probe shows 404s for openapi/swagger endpoints), and the API is tied to the Mac app/plugin ecosystem rather than a cloud-callable service. Missing for 10: a REST/HTTP or OpenAPI-documented API, and independent hands-on corroboration of AI clients actually driving Sketch via MCP.

   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   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 Sketch
   Sketch~partialprobed6/10

   Sketch publishes an official vanilla JavaScript API, a CLI (sketchtool), plugin manager (skpm), and a documented sketch:// URL scheme for integrating into workflows and server apps, which constitute genuine official SDKs/APIs. However, there's no OpenAPI spec, no REST API, and probes confirm no openapi.json exists; the AI-native story is mostly served via MCP connectivity rather than a broad official SDK ecosystem. Missing for 10: a formal REST/OpenAPI API, multi-language SDKs beyond JS, and independent developer corroboration of building production integrations against these SDKs.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Use the Sketch Plugin Manager `skpm` to publish a new plugin or an update of an existing one.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   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 Sketch
   Sketch~partialclaimed6/10

   Sketch's AI features (docs-14,15,26,27,39) generate suggestions like color palettes, dark-mode variants, layer organization, and placeholder content directly from design data, which counts as AI-generated insights/suggestions inside the product; MCP integration (docs-18,34) also lets AI clients query/act on Sketch data. However, these are largely generative/automation utilities rather than analytic 'insights' about the user's data, and there is no independent/hands-on corroboration of quality or accuracy. missing for 10: independent verification of AI feature accuracy/usefulness, broader insight-generation (e.g., analytics on design usage/trends) beyond visual generation tasks, and clearer separation of AI-insight vs AI-automation claims.

   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it. An instant color palette, ready to use in your document.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   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 drawn
   Sketch—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ 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
   Sketch~partialclaimed4/10

   Sketch.com/ai lists several AI-powered automation features (auto dark-mode conversion, palette generation from a photo, automatic layer renaming/sorting, context-aware placeholder text) that a user can invoke to offload discrete design tasks, which is a form of task delegation. However, these are framed as one-off automated tools rather than a conversational, built-in assistant that takes freeform instructions, and the closest thing to an 'assistant' (docs-16/18/34) actually describes connecting an *external* MCP-compatible AI client to Sketch, not a native in-app assistant. Missing for 10: evidence of a conversational/chat-style built-in assistant, evidence of multi-step task delegation beyond single-purpose generators, and independent hands-on confirmation of these AI features working as described.

   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it. An instant color palette, ready to use in your document.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   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
   Sketch~partialclaimed6/10

   Sketch documents AI features (auto dark-mode conversion, color palette generation, layer renaming, placeholder text replacement) and explicit MCP-client connectivity so 'any MCP-compatible AI client' can drive design tasks, implying natural-language-driven operation via an external agent. However there is no first-party evidence of an in-app chat/command interface where a user directly types natural-language instructions to Sketch itself — the AI capabilities are either fixed one-click features or routed through external MCP clients. Missing for 10: a native in-app natural-language command interface, hands-on/independent verification that MCP-driven natural-language commands actually work end-to-end.

   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”

   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 drawn
   Sketch—none0/10

   Direct probing found no OpenAPI/Swagger spec at any standard location (all candidates 404), and no docs reference a machine-readable API spec; Sketch offers a JS plugin API and MCP integration but no downloadable OpenAPI-equivalent.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”

   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
   Sketch—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ 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 Sketch
   Sketch~partialclaimed5/10

   Sketch's AI features (sketch-docs-14,15,26,27,39) cover contextual copy replacement, automatic layer organization, dark-mode conversion, and color-palette extraction from a photo, and it can connect to MCP AI clients for code generation—but there is no evidence of built-in image generation or background removal tools. missing for 10: image generation, background/foreground removal, content-aware fill (beyond text), independent hands-on verification of AI feature quality.

   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it. An instant color palette, ready to use in your document.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   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 to Claude Design
   Sketch~partialclaimed4/10

   Sketch's AI page describes narrow, tool-specific AI features (auto light/dark mode conversion, photo-to-palette, code-to-design 1:1 fidelity, placeholder text replacement, layer auto-organization, and MCP-client integration to 'recreate text styles, colors, UI components, and even entire pages') rather than an open natural-language prompt that a designer types to generate an original first-draft layout or mockup from scratch. This is closer to targeted AI utilities layered onto existing designs than a general prompt-to-mockup generator. Missing for 10: evidence of a text-box/chat interface where a designer types a free-form prompt (e.g. 'design a pricing page') and Sketch outputs an original layout/mockup, and any hands-on or independent verification of AI generation quality.

   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it. An instant color palette, ready to use in your document.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”

   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 Sketch
   Sketch~partialclaimed5/10

   Sketch's AI features include layer-level bulk actions (auto sort/rename/align layers, replacing placeholder text across every layer, swapping light/dark components) and its CLI/plugin API (`sketchtool`, JS API) allow scripted operations across assets, which supports some automation-at-scale. However, there's no evidence of explicit multi-document/multi-project bulk operations or a documented batch API for large-scale item processing beyond within-document layers. Missing for 10: cross-file/cross-project batch operations, explicit bulk API endpoints, and independent verification of scale performance.

   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”

   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 Sketch
   Sketch~partialclaimed4/10

   Sketch offers document-level version history via 'starred versions' that lets you track changes, control which versions are visible/published, and effectively roll back to prior states, which could cover AI-generated design changes; but there is no evidence of a dedicated 'automation' concept (e.g., saved AI workflows/scripts) with its own versioning, diff/review, or rollback mechanism distinct from general document history. missing for 10: evidence of versioning/rollback specifically for AI-generated automations/workflows (not just document snapshots), a review/diff UI for AI changes, and any audit trail tied to MCP/AI actions.

   • [claimed-docs] “starring a version will publish any changes as a Library update. Any unstarred versions after that won’t become Library updates.”
   • [claimed-docs] “When you star a version in a Library document, anyone using that Library will receive a Library update.”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document's history, set which versions Viewers and Guests can see”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document’s history, set which versions Viewers and Guests can see, and contro…”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”

   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 Claude Design
   Sketch—none0/10

   The evidence pack covers developer handoff, prototyping, symbols, versioning, plugins, and AI features, but contains no mention of in-file commenting, @mentions, or thread resolution—core to this collaboration story. Community notes even highlight Sketch's historical lag on real-time collaboration features versus competitors, but nothing confirms comment/mention/resolve functionality exists.

   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”

   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 Claude Design
   Sketch—none0/10

   No evidence in the pack documents live-cursor or simultaneous real-time multiplayer editing in Sketch; the only related community comment explicitly notes that as of late 2020 Sketch still lacked real-time collaboration ('the ability to collaborate in real-time' was still 'soon'), and Figma is cited as having this as its 'killer USP' that Sketch lacks.

   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”
   • [community] “A browser-based version of Sketch would be huge - this is Figma's killer USP at the moment.”

   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 Sketch
   Sketch~partialcommunity5/10

   Sketch supports reusable Styles and Symbols for colors, text, and components across designs, and its AI features can generate named color variables and swap light/dark mode components automatically, giving some token/theme-like behavior. However, there is no evidence of a first-class 'variables with modes' system (e.g., defining semantic tokens with multiple named modes/themes applied project-wide) comparable to dedicated design-token tooling. Missing for 10: explicit variables/tokens feature with mode switching across spacing/typography, first-party documentation of a mode system, and independent hands-on confirmation of theme application at scale.

   • [claimed-docs] “When you make changes to a Symbol, those changes appear everywhere you use it in your designs.”
   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it.”
   • [claimed-docs] “Drop in a photo and get a full set of named color variables that complement it. An instant color palette, ready to use in your document.”
   • [claimed-docs] “Symbols can speed up your workflow by giving you a way to save and reuse common elements across your designs.”
   • [claimed-docs] “Symbols can speed up your workflow by giving you a way to save and reuse common elements across your designs. When you make changes to a Sym…”
   • [community] “Sketch is great as a design system manager. It's not all that great as a sketching tool (in spite of the name) and is a terrible photo edito…”

   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 Sketch
   Sketch~partialcommunity6/10

   Sketch's Symbols documentation confirms reusable components that stay linked to their source (edits propagate everywhere) and supports nested Symbols for complex structures, and community reviews praise Sketch's DRY, component-based design system workflow. However, the evidence never explicitly documents a 'variants' feature or per-instance overrides (e.g., swappable states/overrides on symbol instances) as Figma-style components do. Missing for 10: explicit documentation of variant properties and per-instance override controls, independent hands-on confirmation of override behavior.

   • [claimed-docs] “When you make changes to a Symbol, those changes appear everywhere you use it in your designs.”
   • [claimed-docs] “Nested Symbols give you finer control over complex designs.”
   • [claimed-docs] “Symbols can speed up your workflow by giving you a way to save and reuse common elements across your designs.”
   • [claimed-docs] “Symbols can speed up your workflow by giving you a way to save and reuse common elements across your designs. When you make changes to a Sym…”
   • [community] “Sketch is great as a design system manager. It's not all that great as a sketching tool (in spite of the name) and is a terrible photo edito…”
   • [community] “It's light, fast, cheap, easy to use and has excellent support for reusable components, making working with design systems a breeze. Adobe h…”

   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 Sketch
   Sketch✓fullcommunity7/10

   Sketch's docs explicitly describe Libraries where starring a version publishes changes as a controlled Library update, letting Editors receive updates while Viewers/Guests see only chosen versions, and Symbols propagate style/component changes across all instances. Community commentary corroborates Sketch's strength as a 'design system manager' built around reusable symbols/libraries. Missing for 10: independent hands-on verification of multi-project library update propagation at scale, and documentation of failure modes/conflicts when libraries diverge.

   • [claimed-docs] “starring a version will publish any changes as a Library update. Any unstarred versions after that won’t become Library updates.”
   • [claimed-docs] “When you star a version in a Library document, anyone using that Library will receive a Library update.”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document's history, set which versions Viewers and Guests can see”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document’s history, set which versions Viewers and Guests can see, and contro…”
   • [claimed-docs] “When you make changes to a Symbol, those changes appear everywhere you use it in your designs.”
   • [claimed-docs] “Symbols can speed up your workflow by giving you a way to save and reuse common elements across your designs.”
   • [community] “Sketch is great as a design system manager. It's not all that great as a sketching tool (in spite of the name) and is a terrible photo edito…”
   • [community] “It's light, fast, cheap, easy to use and has excellent support for reusable components, making working with design systems a breeze. Adobe h…”

   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 to Claude Design
   Sketch~partialclaimed5/10

   Sketch's AI page claims direct frame-to-code generation with '1:1 visual fidelity' and MCP-based AI client integration, plus browser-based developer handoff for inspecting specs, which together approximate design-to-code output; however this is entirely first-party marketing with no independent hands-on verification of code quality, supported frameworks, or shippability. missing for 10: independent/community confirmation that generated code is production-ready, details on output format/frameworks, and evidence of real-world dev usage of this AI code feature.

   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser”
   • [claimed-docs] “any developer can grab the information they need for any part of a design, at any time... they won't even need the Mac app (or a Mac) as it …”

   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 Sketch
   Sketch✓fullclaimed8/10

   Sketch's developer handoff docs explicitly confirm free developer invites to inspect designs in-browser without needing the Mac app or a Mac, and note developers can grab measurements/info for any part of a design at any time; code snippet generation (CSS/iOS/Android) is a longstanding Sketch inspector feature implied by 'grab the information they need' though not explicitly enumerated per-platform in this pack. missing for 10: explicit doc citation naming CSS/iOS/Android code snippet export, and independent hands-on confirmation of the inspect panel's snippet output.

   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser”
   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free”
   • [claimed-docs] “any developer can grab the information they need for any part of a design, at any time... they won't even need the Mac app (or a Mac) as it …”
   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free — they won't even need the Mac app (or a Mac) as it all happens in a…”
   • [claimed-docs] “any developer can grab the information they need for any part of a design, at any time”
   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser.”

   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 Sketch
   Sketch~partialprobed5/10

   Sketch exposes a JavaScript plugin API, a CLI (sketchtool), a URL scheme, and MCP-based AI integrations for asset creation and design manipulation, showing meaningful programmatic access beyond the UI. However, there's no evidence of a comprehensive REST/public API covering all UI functions (e.g., prototyping links, sharing/versioning, symbol libraries, workspace permissions) — openapi probes 404'd and docs focus on plugin/CLI/AI hooks rather than full UI parity. missing for 10: a documented full REST/GraphQL API covering all UI actions, evidence that non-plugin workflows (sharing, prototyping, library publishing) are API-accessible, and independent confirmation of API completeness.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   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 Sketch
   Sketch~partialcommunity4/10

   Sketch documents use the open `.sketch` format (a zipped JSON+binary archive) rather than a proprietary opaque format, which supports portability and third-party tooling/git integration per community reports. However, there's no evidence of a full account/workspace-level export tool for bulk data extraction (comments, version history, workspace settings) to enable a clean 'export everything and leave' migration. missing for 10: bulk workspace/account export feature, documented data-portability/migration guide, independent confirmation of successful full data export.

   • [claimed-docs] “Sketch stores documents in .sketch format, a zipped archive of JSON formatted data and binary data such as images.”
   • [claimed-docs] “Sketch stores documents in `.sketch` format, a zipped archive of JSON formatted data and binary data such as images.”
   • [community] “The file format is basically zipped json files, so there's a robust plugin ecosystem and you can do things like git integration pretty easil…”

   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 Sketch
   Sketch~partialcommunity7/10

   Sketch provides a documented plugin API (JavaScript, ES6, macOS framework access), a CLI/manager (skpm) for publishing and installing plugins, and manual plugin installation, and community sources independently confirm Sketch has 'a massive collection of plugins that forms a large part of its appeal' and a 'robust plugin ecosystem.' However, no evidence names a curated marketplace/directory or specific plugin categories like icon libraries, data fillers, or accessibility checkers. Missing for 10: an official plugin marketplace/directory listing, explicit examples of icon/data-filler/accessibility-checker plugins, and any count or curation of the ecosystem.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Use the Sketch Plugin Manager `skpm` to publish a new plugin or an update of an existing one.”
   • [claimed-docs] “you can install plugins by simply moving them into the Plugins folder yourself.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [community] “The file format is basically zipped json files, so there's a robust plugin ecosystem and you can do things like git integration pretty easil…”
   • [community] “Sketch has been widely adopted for UI design. It's simpler than Adobe Illustrator, lighter in resources and subjectively feels far less clun…”

   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 Sketch
   Sketch~partialclaimed5/10

   The pricing page evidence lists enterprise-tier features like SSO, SCIM provisioning, permissions groups, and project archiving, implying a tiered structure, and sketch-docs-18 explicitly states AI/MCP features carry 'no tokens to buy, no extra tiers, no add-ons,' which speaks directly to AI-feature gating. However, there is no evidence of explicit seat-type definitions, plan names, or per-seat pricing tables that a PM could use to compare procurement options. Missing for 10: explicit seat-type/tier naming and pricing amounts, a full feature-by-tier comparison matrix, and independent confirmation that AI gating claims match published plans.

   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “SCIM provisioning”
   • [claimed-docs] “Permissions groups”
   • [claimed-docs] “Single Sign-On (SSO) * Project archiving * Permissions groups”
   • [claimed-docs] “Learn how Single Sign-On (SSO) and SCIM provisioning work in Sketch, and find step-by-step guides to get set up.”

   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
   Sketch—none0/10

   The evidence pack only shows free access for developers to inspect/hand-off designs in a browser (no Mac needed) and a legacy 'no forced upgrade' licensing note, but there is no evidence of a free tier that lets a designer actually create/edit designs or collaborate in real time without a paid seat — Sketch is fundamentally a purchased desktop app for designers. Community notes even highlight it lacked real-time collaboration for years and requires a Mac/license to design at all.

   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free”
   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free — they won't even need the Mac app (or a Mac) as it all happens in a…”
   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser.”
   • [community] “Newer versions of Sketch open old files just fine, and licenses are valid for any version. Sketch licenses do not 'expire', you simply can't…”
   • [community] “You don't have to pay to keep using Sketch, as long as you're ok with not upgrading. Unlike Adobe creative cloud that stops functioning the …”
   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”

   proof ↗⚑ 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
   Sketch—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location options for Sketch's Workspace/cloud data; only SSO/SCIM/permissions security features are documented, none addressing data residency choice.

   ⚑ 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
   Sketch—none0/10

   No evidence in the pack addresses AI training data opt-out, privacy policy on model training, or any data-usage controls specific to AI training; Sketch's AI features (e.g., MCP integration, image-to-palette) are documented but nothing states whether user design data is used to train models or how to opt out.

   ⚑ 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
   Sketch—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or data export/erasure mechanisms for AI-native users; only unrelated SSO/SCIM/permissions and AI-feature docs are present.

   ⚑ 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
   Sketch—none0/10

   No evidence in the pack addresses telemetry, analytics, or usage-tracking opt-out settings for Sketch; the docs and community items cover features, pricing, and performance, not privacy/telemetry controls. Missing for 10: any mention of telemetry collection, opt-out settings, privacy policy details on usage data, or admin controls to disable analytics.

   ⚑ 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 drawn
   Sketch~partialclaimed4/10

   Sketch's docs show interactive prototyping via hotspots/links, overlays, hover/press/toggle triggers, and scrolling areas, which cover some 'feel like the real product' interactions, but there is no evidence of animated transitions between states, conditional logic, or variables — capabilities competitors highlight for advanced prototyping. Missing for 10: animation/transition effects between artboards, conditional logic or variable-driven states, and any documented scroll-triggered animation beyond basic scrolling areas.

   • [claimed-docs] “Create links or Hotspots to navigate between different frames or trigger Overlays.”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “Show Overlays (e.g. menus, dropdowns or dialogs) that appear when you click, press or hover over another layer.”

   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 Sketch
   Sketch✓fullclaimed8/10

   Sketch's own docs describe hotspots/links between frames, overlays (menus/dropdowns/dialogs), and hover/press/toggle triggers plus scrolling areas — directly matching the story's triggers/transitions/overlays without code, and mobile preview lets designers play prototypes on a real device. Missing for 10: independent hands-on reviews specifically praising the prototyping feature (community evidence focuses on performance/native-app debates, not prototyping quality) and no detail on transition animation styles/timing options.

   • [claimed-docs] “Create links or Hotspots to navigate between different frames or trigger Overlays.”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “Show Overlays (e.g. menus, dropdowns or dialogs) that appear when you click, press or hover over another layer.”
   • [claimed-docs] “View your documents on the go, play prototypes on a real device, and mirror designs as you edit them on your Mac.”

   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 drawn
   Sketch—none0/10

   The evidence pack contains no mention of auto layout, resizing constraints, or layout grids for Sketch frames — it covers prototyping, symbols, plugins, AI features, and collaboration but nothing about responsive frame behavior. Missing for 10: any docs or claims about auto layout, constraint-based resizing, or grid systems that make frames responsive.

   ⚑ 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 Sketch
   Sketch~partialcommunity6/10

   Docs confirm non-destructive boolean operations (Union/Subtract/Intersect/Difference) and shape styling (fills, borders, shadows), core vector-editing capabilities for interface design. However, the evidence pack contains no explicit mention of pen/path tools or precise alignment/grid features, and one community comment notes Sketch's vector-editing is 'less buggy' in comparison but still implies some bugginess relative to Figma. Missing for 10: explicit documentation of pen tool/path editing, alignment/distribution tools, and independent hands-on corroboration of vector precision.

   • [claimed-docs] “Create a new shape from two or more shapes with non-destructive boolean operations — Union, Subtract, Intersect and Difference.”
   • [claimed-docs] “Apply a fill, border, drop shadow, inner shadow or bitmap layer to a shape.”
   • [community] “Figma is rather performant (to the point where it outruns Sketch in typical day-to-day design tasks), and their vector-editing is less buggy…”

   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 drawn
   Sketch~partialclaimed3/10

   The pack only hints at asset export via the `sketchtool` CLI ("Create assets with a single command") and never documents the actual Export panel, per-layer presets, scale factors, or slice tooling explicitly. Missing for 10: documentation of PNG/SVG/PDF format options, per-layer export presets, scale multipliers, and slice creation UI/behavior.

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”

   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 drawn
   Sketch~partialcommunity6/10

   Sketch documents its .sketch file format as a zipped archive of JSON and binary data (sketch-docs-23/47), and community evidence confirms this enables a plugin ecosystem and git-style tooling outside the vendor app (sketch-comm-14). However, this is not a formally published open spec/standard with versioned schema docs, and there's no independent tooling ecosystem comparable to open formats like SVG; the developer-handoff features are more about inspection than format portability. Missing for 10: a formal published format specification/schema documentation, third-party tools that read/write .sketch independent of Sketch's own SDK, and any standards-body or open-format commitment.

   • [claimed-docs] “Sketch stores documents in .sketch format, a zipped archive of JSON formatted data and binary data such as images.”
   • [claimed-docs] “Sketch stores documents in `.sketch` format, a zipped archive of JSON formatted data and binary data such as images.”
   • [community] “The file format is basically zipped json files, so there's a robust plugin ecosystem and you can do things like git integration pretty easil…”

   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 Sketch
   Sketch~partialclaimed5/10

   Sketch's docs describe 'starred versions' that let designers mark important updates in a document's history and control which versions become Library updates or are visible to Viewers/Guests, which covers naming/milestone-marking, but the evidence never describes a compare/diff view between versions or an explicit 'restore to any earlier state' UI. Missing for 10: documented version comparison/diff tooling, explicit restore-to-previous-version workflow, and any independent/hands-on confirmation of these version-history mechanics.

   • [claimed-docs] “starring a version will publish any changes as a Library update. Any unstarred versions after that won’t become Library updates.”
   • [claimed-docs] “When you star a version in a Library document, anyone using that Library will receive a Library update.”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document's history, set which versions Viewers and Guests can see”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document’s history, set which versions Viewers and Guests can see, and contro…”

   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