Figma vs Sketch

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

   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

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
   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

   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

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

   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

Agent access

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

   weight 2 · round drawn
   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

   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

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Figma~partialclaimed5/10

   Figma's REST API explicitly supports CI/CD-style automation for variables sync ('Integrate Figma directly with continuous integration (CI) systems', 'useful for needs like CI/CD implementations... webhooks... service accounts') and webhooks/plan tokens allow non-interactive, user-agnostic access, which is real evidence of headless automation capability. However this is scoped mainly to variables/webhooks/library-analytics rather than full design-file manipulation or MCP server operation, and there's no evidence of a general-purpose CLI or headless rendering/export pipeline for arbitrary Figma actions. missing for 10: evidence of a full headless CLI or automation runner covering arbitrary design operations (not just variables/webhooks), independent/hands-on confirmation of CI usage, and headless operation of the MCP server itself.

   • [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] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [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] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account.”

   proof ↗⚑ flag

   Sketch~partialcommunity5/10

   Sketch documents a command-line tool (`sketchtool`) for scripted asset creation and claims it can integrate 'into your workflows and server applications, on any platform,' which points at CI/headless automation use. However, this is only first-party doc language with no independent verification, and community evidence confirms Sketch itself is strictly Mac-native and the vendor has refused Windows/Linux support, undercutting the 'any platform' claim. Missing for 10: independent CI/automation examples or case studies, clarity on macOS-only runtime requirements for sketchtool, and confirmation of non-interactive/headless execution in real 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.”
   • [community] “It's not just their commitment to Desktop, but their commitment specifically to not move off MacOS where they have stated that they 'will no…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   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

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Figma
   Figma✓fullprobed8/10

   Figma ships an official, well-documented MCP server (local and remote) that lets AI clients read/write Figma content, extract design context, generate code, and more, with detailed docs on installation, tools, and custom rules (figma-docs-1/3/5/38/59/67/68/69, figma-probe-3). This is a first-party, actively maintained integration point for agentic MCP clients. Missing for 10: independent/hands-on community verification that the MCP connection works reliably in practice (community evidence only discusses unrelated Figma pain points, not MCP specifically).

   • [claimed-docs] “Write to the canvas: Create and modify native Figma content directly from your MCP client.”
   • [claimed-docs] “Extract design context: Pull in variables, components, and layout data directly into your IDE.”
   • [claimed-docs] “Generate designs from live UI: Use a supported MCP client to capture the live UI of your web app or site and send it to new and existing Fig…”
   • [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] “Figma's remote MCP server makes it possible to connect directly to your Figma files without needing to install Figma's desktop app.”
   • [claimed-docs] “`get_variable_defs` extracts the **variables and styles** used in your selection (color, spacing, typography, etc).”
   • [claimed-docs] “Define project-level instructions to help guide the AI toward consistent, high-quality output.”
   • [probe] “official MCP server documented at https://developers.figma.com/docs/figma-mcp-server/”

   proof ↗⚑ flag

   Sketch✓fullclaimed7/10

   Sketch documents that users can connect any MCP-compatible AI client to Sketch itself, positioning Sketch as an MCP server that AI agents can plug into, with no extra tiers or tokens required. Missing for 10: independent/hands-on verification that the MCP connection works reliably, and detailed technical docs on the server's capabilities/setup beyond marketing copy.

   • [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] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Sketch
   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

   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

6. 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

   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

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Figma
   Figma~partialclaimed4/10

   Figma's REST API docs mention OAuth apps that can 'make requests on behalf of other users' without using a personal account, and 'plan access tokens' scoped to an org/enterprise plan, plus service-account-like tokens for CI/CD/webhooks decoupled from an individual user — these are building blocks for issuing a non-personal, scoped credential to an agent. However there is no explicit documentation of granular least-privilege scopes (e.g., read-only vs write, per-file/per-resource permissions) for AI agents or the MCP server specifically. Missing for 10: documented fine-grained OAuth/API scopes selectable for agent credentials, explicit MCP-server auth/scoping guidance, and any independent confirmation this scoping mechanism is used for AI agents.

   • [claimed-docs] “A plan access token provides API access scoped to an organization or enterprise plan.”
   • [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] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account.”
   • [claimed-docs] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account”

   proof ↗⚑ flag

   Sketch—none0/10

   Evidence shows MCP connectivity, SSO, SCIM provisioning, and permissions groups, but nothing about issuing scoped or least-privilege API credentials/tokens specifically for agents; permissions groups and SSO are user-level access controls, not credential scoping mechanisms. Missing for 10: any documentation of API tokens, scoped keys, or credential issuance workflow tailored to agent use.

   • [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”

   proof ↗⚑ flag

8. 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

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Figma
   Figma✓fullclaimed7/10

   Figma's REST API docs explicitly describe creating and managing webhooks and subscribing to events like comments or new file versions, with a dedicated webhooks-endpoints reference, directly matching the user story. Missing for 10: independent or hands-on corroboration that webhook subscriptions work reliably in practice, and fuller documentation of the range of supported event types beyond the couple of examples given.

   • [claimed-docs] “Create and manage [webhooks](/docs/rest-api/webhooks-endpoints/)”
   • [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] “useful for needs like CI/CD implementations, logging, creating user-agnostic webhooks, and other tasks that you normally wouldn't want gated…”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in 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 …”

   proof ↗⚑ flag

   Sketch—none0/10

   No evidence of Sketch offering webhooks or event subscription mechanisms; the product exposes a plugin API, CLI (sketchtool), URL scheme, and MCP integration for AI clients, but nothing about webhook subscriptions for events. This is a fair axis for a platform with an API/integration ecosystem, so absence of evidence yields 'none'.

   • [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.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Sketch
   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

   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

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

   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

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

   weight 3 · round to Sketch
   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

   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

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

   weight 2 · round to Sketch
   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

   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

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Sketch
   Figma—none0/10

   Figma's REST API docs describe endpoints and there's a separate OpenAPI spec repo, but no evidence shows an interactive reference with runnable/try-it-now examples; probes for standard openapi.json/swagger endpoints on the docs site returned 404s, and no docs mention interactive code sandboxes or live example runners.

   • [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] “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

   Sketch~partialprobed3/10

   Sketch documents a JavaScript plugin API and invites developers to 'Try the Sketch JavaScript API now, directly within Sketch,' suggesting some interactive API exploration, but there is no evidence of a full interactive reference with runnable code examples (OpenAPI/swagger probes all 404, no dedicated API-explorer docs found). missing for 10: dedicated interactive API reference UI, runnable code examples/sandbox, OpenAPI/swagger spec, independent confirmation of the 'try now' feature.

   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [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

2. 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

   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

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

   weight 1 · round drawn
   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

   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

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Figma
   Figma~partialclaimed3/10

   Figma publishes a REST API changelog documenting endpoint additions/renames (e.g., v2 folders endpoints, projects→folders rename) and an OpenAPI spec repo, showing some versioning practice, but there is no explicit documented deprecation policy (timelines, sunset notices, migration guarantees) for the REST API or MCP server. missing for 10: explicit deprecation policy statement, version support timelines, sunset/EOL notices for old endpoints.

   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”
   • [claimed-docs] “Added folders endpoints for plans with nested folders enabled: GET /v2/teams/:team_id/folders”
   • [claimed-docs] “These rename "projects" to "folders" and add subfolder traversal.”
   • [claimed-docs] “A plan access token provides API access scoped to an organization or enterprise plan.”

   proof ↗⚑ flag

   Sketch—none0/10

   Sketch exposes a JavaScript plugin API, sketchtool CLI, and MCP integration, and claims the JS API is 'fully supported between releases' (sketch-docs-44), but there is no documented API versioning scheme or deprecation policy — probes for OpenAPI specs return 404 and no changelog/deprecation docs are present in the evidence pack.

   • [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

Ai

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

   weight 1 · round drawn
   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

   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

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

   weight 2 · round to Figma
   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

   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

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

   weight 2 · round drawn
   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

   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

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Figma
   Figma~partialclaimed4/10

   Figma's webhooks let you observe events (comments, new versions, library usage) and forward them to external systems (figma-docs-21, figma-docs-53, figma-docs-61), which can be wired into automation elsewhere, but Figma itself has no built-in rule-builder or 'if event then action' automation engine — plugins run only on user invocation, not on trigger conditions (figma-docs-36). missing for 10: a native rules/automation UI or API where users define event-condition-action logic inside Figma, and any evidence of automatic (non-user-invoked) action execution.

   • [claimed-docs] “Create and manage [webhooks](/docs/rest-api/webhooks-endpoints/)”
   • [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] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   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

   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

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

   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

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

   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

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

   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

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

   weight 3 · round to Sketch
   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

   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

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

   weight 2 · round to Sketch
   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

   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

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 Figma
   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

   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

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

   weight 3 · round to Sketch
   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

   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

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

   weight 2 · round drawn
   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

   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

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

   weight 3 · round to Sketch
   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

   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

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Figma—none0/10

   Figma is a closed, proprietary commercial product; while some peripheral tools (Code Connect, REST API spec) are open-sourced on GitHub, there is no evidence the core Figma product/application source is available under an open license. Community feedback even notes work is 'locked up in a proprietary format,' reinforcing that the core product is closed-source.

   • [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 - …”
   • [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 repository contains the OpenAPI specification and Typescript types for the Figma REST API”

   proof ↗⚑ flag

   Sketch—none0/10

   Sketch is a proprietary, closed-source commercial design tool; the file format spec (sketch-document) is open, but there is no evidence the application source code itself is under an open license. No evidence contradicts closed-source status.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Figma—none0/10

   Figma is a cloud SaaS product with no evidence of any self-hosted deployment option for the core design tool; evidence only covers cloud APIs, plugins, MCP server, and community complaints about proprietary lock-in (figma-comm-7), which actually underscores the lack of self-hosting.

   • [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

   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

Plugins

1. developerA documented plugin API with typings and samples lets me build and distribute my own editor extensions

   weight 2 · round drawn
   Figma✓fullclaimed8/10

   Figma documents a full Plugin API with read/write access to editors, custom UI, and widgets, plus dedicated docs site (developers.figma.com/docs/plugins) and a marketplace for publishing/distributing plugins and widgets (public or private). Combined with the OpenAPI/TypeScript REST spec and Code Connect samples, this constitutes a documented, typed extensibility platform for developers. Missing for 10: explicit mention of TypeScript typings specifically for the Plugin API (typings confirmed only for REST API) and independent hands-on developer reviews of the plugin-building experience.

   • [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] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”
   • [claimed-docs] “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] “Unlike plugins that run for a specific person, everyone can see and interact with the same widget.”
   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”

   proof ↗⚑ flag

   Sketch✓fullcommunity8/10

   Sketch provides a dedicated developer portal (developer.sketch.com) with a documented JavaScript plugin API, in-browser API tester, official vanilla JS API stable across releases, plugin manager (skpm) for publishing/distributing plugins, and manual install support, plus CLI/URL-scheme integration options. Missing for 10: independent hands-on developer reviews confirming ease of building complex plugins and richer typings/type-definition documentation beyond API reference mentions.

   • [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] “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.”
   • [claimed-docs] “you can install plugins by simply moving them into the Plugins folder yourself.”
   • [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

2. 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

   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

Pricing

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

   weight 1 · round drawn
   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

   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

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

   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

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

   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

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

   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

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

   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

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

   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

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

   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

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

   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

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

   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

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

   weight 3 · round to Sketch
   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

   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

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

   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

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

   weight 1 · round to Sketch
   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

   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

3. developerSelf-host the full design platform on my own infrastructure under an open-source license

   weight 2 · round drawn
   Figma—none0/10

   Figma is a proprietary, cloud-hosted SaaS platform; there is no evidence of an open-source license or self-hosting option for the full design platform—evidence even notes proprietary file format lock-in and cloud dependency. Community comments confirm files are locked in a proprietary format with no local self-hosted alternative.

   • [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

   Sketch—none0/10

   Sketch is a proprietary Mac-based SaaS/desktop product with no evidence of an open-source license or self-hostable infrastructure; community discussion even highlights Sketch's refusal to leave macOS or move to browser/cloud-native architecture, the opposite of self-hosting. No docs, licensing pages, or repos indicate an open-source core platform available for self-hosting.

   • [community] “It's not just their commitment to Desktop, but their commitment specifically to not move off MacOS where they have stated that they 'will no…”
   • [community] “A browser-based version of Sketch would be huge - this is Figma's killer USP at the moment.”
   • [claimed-docs] “Sketch stores documents in .sketch format, a zipped archive of JSON formatted data and binary data such as images.”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   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

   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