Sketch vs Spline

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

   Spline✓fullprobed8/10

   Spline ships a dedicated MCP Server (bundled in desktop app) that lets Claude, Cursor, Codex, VS Code, Antigravity and ChatGPT drive the live editor to create/modify designs, plus a write-capable Code API for programmatic scene manipulation and webhooks/Real-time API for external event-driven updates. This goes beyond read-only access into genuine programmatic creation/modification. Missing for 10: independent hands-on validation of the MCP server's write actions and no public OpenAPI spec was found (openapi probe 404s), so full API surface is only documented, not independently verified.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “the desktop app gives you a few things the browser can't: **tabs** for working across several files, **system fonts**, and **MCP** support”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “Spline works fully in the browser, but the desktop app gives you a few things the browser can't: **tabs** for working across several files, …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Spline~partialprobed4/10

   Spline documents multiple export/programmatic surfaces (export-as-code for Vanilla JS/Three.js/React/Next.js/r3f, self-hosted ZIP export, Code API, Real-time API, webhooks) and an MCP server that lets agents like Claude/Cursor drive the editor, but none of the docs explicitly describe an agent invoking a screenshot/image render or export action through these interfaces — the MCP surface is framed as scene building/editing, not export/rendering. Missing for 10: explicit MCP or API tool for triggering exports/screenshots/renders programmatically, and independent confirmation this works end-to-end for an agent.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Spline~partialprobed6/10

   Spline ships an official MCP server bundled with the desktop app that connects Claude, Cursor, Codex, Antigravity and other MCP clients directly to the open editor, and separately offers a Code API, Real-time API and code export (React/Next.js/Three.js/react-three-fiber) that could let an agent read variables and scene structure to implement designs. However the MCP server's documented purpose is to let AI clients drive/edit the Spline scene ('straight into your open editor tab'), not explicitly to pull frames, screenshots, or component mappings as design-context for an external implementation — that specific dev-mode-style extraction flow is not evidenced. Missing for 10: explicit support for screenshot export via MCP/API, frame-level context retrieval, and documented component-mapping extraction for code implementation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

Agent access

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

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

   Spline✓fullprobed9/10

   Spline has a verified llms.txt at docs.spline.design/llms.txt (HTTP 200 probe) plus .md-suffixed doc pages that render clean markdown for agent consumption, confirming genuine agent-oriented docs infrastructure. missing for 10: independent third-party confirmation that agents actually consume these docs successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.spline.design/llms.txt # Spline Documentation ## Docs - [Getting Started](https://docs.spline.des…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.spline.design/basics/what-is-spline.md # What is Spline? (/basics/what-is-spline) Spline is a web…”
   • [claimed-docs] “How Spline compares to traditional 3D tools like Blender, Maya and Cinema 4D.”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   Spline is documented purely as a browser/desktop GUI editor with a multiplayer, real-time canvas; its MCP server explicitly requires the desktop app with 'your open editor tab' running interactively, and no CLI, headless render mode, or CI-triggerable build/export process is documented anywhere in the evidence pack. Webhooks and the Real-time API only affect published/runtime scenes, not the design-time editor pipeline, so there is no path to running Spline itself headlessly in automation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   All evidence describes Spline shipping an MCP *server* (docs-13, docs-25, docs-36, docs-53) that external MCP clients like Claude/Cursor/Codex connect to — the reverse of this story, which asks whether a user can plug external MCP servers into Spline so its own AI agent can use their tools. No evidence shows Spline acting as an MCP client or consuming third-party MCP tool servers.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”

   proof ↗⚑ flag

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

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

   Spline✓fullprobed8/10

   Spline documents an official MCP server bundled in the desktop app that connects Claude, Cursor, Codex, VS Code, Antigravity, and ChatGPT directly to the editor, requiring no separate install/config. This is a clear first-party MCP server offering with dedicated docs. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and no detail on the specific tools/capabilities exposed via the server.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Spline~partialprobed7/10

   Spline documents several external-facing interfaces an AI-native user could drive: the Real-time API and Webhooks for event-driven external integration, a Code API for web to control published scenes from external code/UI, and an MCP Server that lets AI coding agents (Claude, Cursor, Codex) manipulate the editor directly. These are genuine documented, public-facing APIs beyond just manual UI use. missing for 10: a formal REST/OpenAPI specification (probe explicitly found no openapi.json/swagger.json at any candidate path), and independent/hands-on corroboration that these APIs work reliably outside vendor docs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   Evidence shows Spline offers an MCP server for connecting AI coding tools to the editor, but there is no mention of scoped or least-privilege API credentials, API keys with permission scopes, or any access-control mechanism for issuing restricted agent credentials. Missing for 10: any documentation of credential/token scoping, permission levels, or least-privilege API key issuance for agents.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

   Spline~partialprobed6/10

   Spline documents a Code API and multiple official code-export targets (Vanilla JS, Three.js, React, Next.js, react-three-fiber) plus a self-hosted runtime export, which functions as an SDK-like integration surface for developers (spline-docs-6, spline-docs-12, spline-docs-17, spline-docs-8). However, a live probe for a formal OpenAPI/SDK spec returned 404s, and there's no independent developer corroboration of SDK usage or versioned package docs beyond the docs site. Missing for 10: dedicated SDK/package documentation (e.g. npm SDK docs), OpenAPI/API reference, and third-party hands-on confirmation of building against these SDKs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

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

   Spline✓fullclaimed7/10

   Spline docs explicitly document a Webhooks feature that allows listening for and responding to external events, triggering actions, updating variables, and reacting to data sent from external sources — directly matching the story. However, this is first-party documentation only with no independent/hands-on corroboration or detail on subscription mechanics (event types, payload schema, delivery guarantees). Missing for 10: independent verification of webhook reliability, detailed event-type/payload documentation, hands-on community testing.

   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”

   proof ↗⚑ flag

Agentic features

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

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

   Spline~partialclaimed4/10

   Spline offers webhooks and a Real-time API that let a published scene 'automatically trigger actions, update variables, and react to data sent from external sources' without a person driving it (spline-docs-9, spline-docs-10, spline-docs-26), which is a form of event-driven automation running unattended. However, this is scene-level reactivity to external events, not a general-purpose scheduled/autonomous agent workflow — the AI Agent and MCP integrations require an open editor tab and active AI-tool session (spline-docs-13, spline-docs-25) rather than running independently in the background. Missing for 10: evidence of scheduled/cron-like autonomous tasks, independent confirmation of webhook automation working in practice, and any agentic workflow that persists without an open editor session.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”

   proof ↗⚑ flag

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

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

   Spline✓fullclaimed7/10

   Spline ships a built-in AI Agent that autonomously builds and edits 3D scenes ('describe what you want and it does the work through the editor itself — creating objects, setting up materials and lighting, animating, wiring interactivity') and a parallel Hana AI Agent for 2D screens, both directly matching the delegated-task story. Missing for 10: independent/hands-on verification of the agent's real-world reliability and scope beyond first-party docs.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ flag

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

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

   Spline✓fullclaimed8/10

   Spline's AI Agent lets users describe what they want in natural language and the editor builds objects, materials, lighting, animation, and interactivity accordingly (spline-docs-3, spline-docs-20, spline-docs-40), and Hana's AI Agent similarly designs UI screens from natural-language descriptions (spline-docs-21, spline-docs-39, spline-docs-54). AI texture generation also works by typing descriptions (spline-docs-4, spline-docs-28). This is reinforced by an MCP server enabling natural-language driven control from external AI clients like Claude/Cursor (spline-docs-13, spline-docs-36). Missing for 10: independent/hands-on user reports confirming natural-language command reliability and breadth of coverage beyond first-party docs.

   • [claimed-docs] “describe what you want and the 3D editor builds it: objects, materials, lighting, animation, interactivity.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”

   proof ↗⚑ flag

Api quality

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

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

   Spline—none0/10

   Spline documents several APIs (Code API, Real-time API, webhooks) but the evidence pack shows no interactive API reference with runnable examples — a probe for OpenAPI/swagger specs returned 404 on all candidate paths, and the docs are plain markdown descriptions rather than an interactive sandbox.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   A direct probe for OpenAPI/swagger specs at common paths returned 404 across all candidates, and no documentation references a downloadable machine-readable API spec; Spline offers a Real-time API and Code API but no OpenAPI equivalent is evidenced.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the OpenAPI probe returned 404s across all candidate paths, and no docs mention version numbers, changelogs, or deprecation timelines for the Real-time API, Code API, or MCP server.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

Ai

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

   weight 1 · round to Sketch
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed3/10

   Spline documents built-in AI features—AI-generated textures via text prompts and an AI Agent/Hana that builds/edits 3D scenes and screens—which is a form of in-editor generative asset creation, but there's no evidence of background removal, content-aware fill, or AI copy/text suggestions inside the editor. missing for 10: background removal, content-aware fill, copy/text suggestions, general image asset generation beyond textures.

   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like **grass**, **concrete**, **wood**, **ceramic**, and **patterns** just by typing!”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

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

   Spline✓fullclaimed7/10

   Spline documents two AI Agents that generate designs from natural-language prompts: the 3D AI Agent creates objects, materials, lighting, animation and interactivity from a description, and Hana's AI Agent designs full 2D screens (layout, type, colour, effects, states) from a text description, which can then be edited by hand. This directly matches the story of generating first drafts/mockups from a prompt. Missing for 10: independent/hands-on verification of the AI Agent's actual output quality, and no third-party reviews or demos confirming real-world reliability of these AI generation features.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs describe single-scene editing, MCP/Code API/webhook integrations, and AI generation features, but nothing indicates batch or bulk processing across many objects, scenes, or files at once (e.g., no scripting loop API, no bulk export/import, no multi-file automation mentioned).

   ⚑ flag

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

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

   Spline✓fullclaimed7/10

   Spline's states/events/actions system, webhooks, and Real-time API let users define rules that trigger actions automatically on events (e.g., 'automatically trigger actions, update variables, and react to data sent from external sources'), which is core automation-depth functionality. missing for 10: independent/hands-on verification of event-rule automation in practice, and more detail on the breadth/complexity of conditional logic supported beyond docs claims.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”

   proof ↗⚑ flag

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

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

   Spline~partialclaimed5/10

   Spline's Version History lets users preview, recover, and manually save previous file states, which would cover the interactivity/automation logic (events, actions, webhooks) embedded in a scene, but this is a whole-file history feature, not a dedicated review/diff mechanism for automations specifically, and no evidence of granular change review or approval workflows exists. missing for 10: automation-specific diffing/review UI, branching or approval workflow, independent confirmation of rollback reliability for complex automations.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

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

   Spline~partialclaimed4/10

   Docs confirm real-time multiplayer editing and that users can 'give feedback in place, the way they would in a 2D design tool,' implying some in-file commenting, but there is no mention of @mentioning teammates or resolving comment threads. missing for 10: explicit mention/tagging of teammates, ability to resolve/close comment threads, dedicated commenting UI documentation.

   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”

   proof ↗⚑ flag

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

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

   Spline✓fullclaimed8/10

   Multiple first-party docs consistently describe Spline as "multiplayer from the ground up," cloud-hosted files enabling several people to edit the same file simultaneously with in-place feedback, similar to 2D design tools — directly matching the story. Missing for 10: explicit mention of live cursors specifically, and no independent/hands-on corroboration of real-time sync quality at scale.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “Spline is two editors that share the same interactivity model, the same real-time collaboration, and the same publishing pipeline.”

   proof ↗⚑ flag

Design systems

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

   weight 2 · round to Sketch
   Sketch~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs mention 'variables and data' only in the context of real-time API/webhooks event data, not design tokens for color, spacing or typography, and the only 'theme' feature found is the editor's own Dark/Light/System UI theme, not a token system applied across a designer's own scenes. No evidence shows reusable style tokens with modes/themes propagated across designs.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline supports **Dark**, **Light**, and **System** themes so you can customize the interface to your preference.”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Spline docs confirm a Components system where reusable objects propagate changes from a main component to all instances (spline-docs-5), which covers the 'linked to source' part of the story. However, there is no evidence of a variants system (multiple named states of a component) or per-instance override capability that persists while staying linked, as seen in dedicated design tools. Missing for 10: documented variants/property sets per component, explicit per-instance override UI, and evidence of overrides surviving source updates.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullcommunity7/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Spline documents component reuse where instances update when the main component changes (spline-docs-5), and pricing mentions a 'Team Library' feature (spline-docs-33), implying some shared-library capability across a team. However, there's no documentation detailing publishing components/styles across separate files or projects, or how updates propagate/are controlled at that scope. Missing for 10: cross-file/cross-project library publishing workflow, versioned/controlled update mechanism, and any independent confirmation of Team Library behavior.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

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

   Spline✓fullclaimed7/10

   Spline documents direct design-to-code export in multiple production-ready formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), plus a Code API for wiring exported scenes into existing codebases, a self-hosted ZIP export bundling assets/runtime, and a native <spline-viewer> web component for drop-in embedding — all clearly aimed at shipping designed 3D/2D scenes into real production code. Missing for 10: independent/hands-on verification that exported code is production-quality and maintainable, and explicit component-to-code sync (e.g., design system tokens/components mapped 1:1 to code components) beyond scene-level export.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: * **Vanilla JS**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “`<spline-viewer>` is a native HTML web component and can be used with most web builders, frameworks, or browsers.”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs describe code export as full-scene exports (Vanilla JS, Three.js, React, Next.js, react-three-fiber) and a Code API for developers, but there is no evidence of a dev-handoff/inspect mode that lets a non-editor viewer inspect a specific layer for measurements, styles, assets, or CSS/iOS/Android snippets without holding an editor seat.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”

   proof ↗⚑ flag

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

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

   Spline~partialprobed5/10

   Spline offers real API-like surfaces for AI-native workflows — a Code API for runtime object/property control (spline-docs-6, -17), a Real-time API and webhooks for external data/events (spline-docs-9, -10, -26), and notably an official MCP server that lets AI clients like Claude/Cursor/Codex drive the live editor tab directly (spline-docs-13, -36, -53) plus an AI Agent that can create objects, materials, lighting and interactivity through the editor (spline-docs-20, -40, -55). However, probing for a formal REST/OpenAPI spec returned 404s across all candidate paths (spline-probe-3), and the documented APIs are scoped to runtime manipulation/events, not full parity with the UI's modeling toolset (booleans, hair systems, physics, gaussian splatting, materials library) — so full UI-equivalent API coverage is not evidenced. missing for 10: a documented comprehensive API/SDK exposing full scene-authoring parity (modeling, materials, physics, animation) rather than just runtime triggers/MCP-driven editor control, and independent confirmation of API completeness.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

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

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

   Spline✓fullclaimed7/10

   Spline documents self-hosted export (full project, assets, and runtime as a self-contained ZIP) and code export in multiple open web formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), giving users a way to take their scene data out of the platform entirely rather than being locked into a proprietary cloud-only format. Missing for 10: no evidence of exporting to standard interchange 3D formats (e.g., glTF/OBJ), no independent/hands-on confirmation that self-hosted exports are truly complete and portable, and no mention of exporting non-visual metadata (variables, version history) alongside the scene.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   Spline is a closed, proprietary commercial design tool; nothing in the evidence pack mentions an open-source license or publicly available source code for the core product (only exported project assets can be self-hosted, which is not the same as open-sourcing the tool's source).

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   Spline is an inherently cloud/multiplayer SaaS editor ('files live in the cloud', 'multiplayer from the ground up') with no evidence of a self-hostable core editor. The 'Self-Hosted' feature only lets users export a finished scene/runtime as a static ZIP for embedding elsewhere — it does not let anyone run the Spline design tool itself on their own infrastructure.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ flag

Plugins

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

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

   Spline—none0/10

   Spline documents a Code API, MCP server, webhooks, and export pipelines for integrating exported scenes into external apps, but there is no evidence of a documented plugin/extension API (with typings and samples) for building and distributing extensions to the Spline editor itself, and an OpenAPI/SDK probe returned 404s. Missing for 10: a documented editor plugin SDK, typings/type definitions for plugin development, and sample plugin code or a plugin marketplace/distribution mechanism.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch~partialcommunity7/10

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

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

   proof ↗⚑ flag

   Spline—none0/10

   No evidence of a plugin community, marketplace, or third-party extensions (icons, data fillers, accessibility checkers) for Spline; the evidence only covers Spline's own built-in features (AI tools, MCP server, code export, materials library).

   ⚑ flag

Pricing

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

   weight 1 · round to Sketch
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed2/10

   Only one evidence item references the pricing page at all, and it's a bare fragment listing a few feature bullets (code/self-hosted export, version history, team library) with no visible seat types, tier names, or explicit AI-feature gating breakdown. Missing for 10: documented tier names/pricing, seat-type definitions, explicit AI feature gating per tier, and any independent corroboration of the pricing page's clarity.

   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

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

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

   Spline~partialclaimed3/10

   Docs describe Spline as 'multiplayer from the ground up' with cloud-based files that several people can edit at once, suggesting collaboration is core to the product rather than gated behind a paid seat, but the evidence pack has no explicit free-tier pricing page detail confirming seat limits, viewer/editor caps, or whether real-time collaboration is unrestricted on the free plan. The one pricing-page snippet (spline-docs-33) lists Code/self-hosted exports, version history, and Team Library without clarifying tier boundaries. missing for 10: explicit free-tier plan page detailing seat/collaborator limits, independent user reports confirming free-tier collaboration works in practice.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls; Spline docs discuss cloud storage, multiplayer, exports and MCP but never a data-region choice. missing for 10: any mention of region/residency options, data center choice, or compliance certifications tied to storage location.

   ⚑ flag

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

   weight 3 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack addresses AI-training data opt-out, privacy settings, or data usage policies for model training; the docs focus entirely on design/collaboration/AI-generation features with no mention of privacy controls or training data exclusion.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   The evidence pack contains no mention of data retention policies, deletion controls, data export for compliance, or privacy/GDPR settings for AI-native users; it covers only design, collaboration, export, and MCP/AI features. Missing for 10: any documentation of data retention settings, account/file deletion controls, or privacy compliance mechanisms.

   ⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   No evidence in the pack addresses telemetry, analytics, or usage tracking opt-out settings for Spline; the docs cover design features, MCP, exports, and collaboration but nothing about privacy/tracking controls. This is a fair axis for a cloud-based SaaS design tool, so absence of evidence yields 'none'.

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

   Spline✓fullclaimed8/10

   Spline's docs strongly evidence advanced prototyping behavior: states/events/actions interaction model, variables and real-time API, webhooks for event-driven reactions, animation, multi-scene transitions, physics, and even code/HTML embedding for custom logic — all built to make prototypes feel like real products. Missing for 10: independent hands-on validation of complex behavior chains (scroll-driven effects specifically) and no dedicated 'scroll trigger' doc beyond general events/actions system.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “On Spline you can create different types of physics simulations, each object can be adjusted to react to gravity and collision forces.”
   • [claimed-docs] “A file can carry one HTML document — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the 3D …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed6/10

   Docs confirm no-code interactivity via states/events/actions (spline-docs-31) and multi-scene transitions via the Events system's Scene Transition action (spline-docs-61), which directly supports triggers and transitions for prototyping. However, 'overlays' are only evidenced via the Code tab feature, which requires writing HTML/CSS/JS (spline-docs-11/24), contradicting the 'no code required' framing for that specific element, and there is no dedicated hands-on or independent account of designers building full clickable multi-screen prototypes end-to-end. Missing for 10: a no-code overlay/layering mechanism, and independent/hands-on evidence of a complete click-through prototype workflow across screens.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “A file can carry one **HTML document** — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the…”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”

   proof ↗⚑ flag

Canvas

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

   weight 2 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Spline—none0/10

   Spline's docs cover 3D modeling, materials, animation, multiplayer, AI generation, and code export, and even mention a 2D canvas (Hana) for interfaces, but nowhere is there mention of auto layout, constraints, or responsive grid systems that would let frames resize like real UI layouts. Missing for 10: any documentation of auto-layout, constraint-based resizing, or grid systems for frames.

   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed5/10

   Docs confirm a pen tool for custom 2D shapes (spline-docs-43), boolean operations (Union/Subtract/Intersect) for objects (spline-docs-60), a dedicated 2D canvas with vector networks for interfaces (spline-docs-38), and extrusion turning 2D shapes into 3D (spline-docs-42) — core vector-editing primitives are present. However, there's no documentation of precise alignment/distribution tools, grids, or snapping, and no independent/hands-on evidence validating these tools for serious interface design work versus its primary 3D focus. Missing for 10: alignment/snapping tooling documentation, path-editing depth (e.g., bezier handle controls), independent corroboration of professional UI design usage.

   • [claimed-docs] “The pen tool enables you to create custom 2D shapes in the 3D space. It works in a familiar way to other 2D or UI design tools.”
   • [claimed-docs] “There are 3 different Boolean Operations that you can apply to a set of selected 3D objects: Union ... Subtract ... Intersect”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Although 2D objects don't have a depth parameter, they can quickly become 3D using a modeling operation called **Extrusion**.”

   proof ↗⚑ flag

Files

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

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

   Spline—none0/10

   Spline's documented export options are all code/runtime based (Vanilla JS, Three.js, React, Next.js, react-three-fiber, self-hosted ZIP, spline-viewer web component) with no mention of PNG/SVG/PDF raster/vector asset export, per-layer presets, scales, or slices anywhere in the evidence pack.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

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

   Spline~partialclaimed5/10

   Spline's native .spline file format itself is never documented as open or given a public schema; instead portability is achieved indirectly via export mechanisms — code export to Vanilla JS/Three.js/React/Next.js/react-three-fiber, a self-hosted ZIP with the runtime, and a Code API — which let designs be used outside the editor without exposing/documenting the native format. missing for 10: an open/published spec for the native .spline file format, third-party tooling that reads/writes it directly, independent confirmation that exported code is a full fidelity substitute for the file itself.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”

   proof ↗⚑ flag

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

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

   Spline—none0/10

   Spline is a cloud-based, closed-source SaaS design tool; the only 'self-hosted' feature documented is exporting a finished 3D scene as a self-contained ZIP for use in your own web app, not self-hosting the design editor/platform itself. There is no evidence of an open-source license, on-prem installer, or self-hostable server for the full editor.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”
   • [claimed-docs] “It's web-based. Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ flag

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

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

   Spline~partialclaimed6/10

   Docs confirm a Version History feature that lets users preview all saved versions, track changes, and restore/recover earlier file states, plus manually save new versions ([spline-docs-15],[spline-docs-29],[spline-docs-33]). However, there is no evidence of explicitly naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: explicit naming/labeling of milestone versions, a diff/compare UI between versions, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag