Figma 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 to Figma
   Figma✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Figma
   Figma✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   • [claimed-docs] “useful for needs like CI/CD implementations, logging, creating user-agnostic webhooks, and other tasks that you normally wouldn't want gated…”
   • [claimed-docs] “Integrate Figma directly with continuous integration (CI) systems.”
   • [claimed-docs] “The Variables REST API includes endpoints for querying, creating, updating, and deleting variables.”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files. For example: a collaborator comments on a file, or you add a new version…”
   • [claimed-docs] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account.”

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Figma
   Figma✓fullprobed9/10

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

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

   proof ↗⚑ flag

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

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

   • [claimed-docs] “A plan access token provides API access scoped to an organization or enterprise plan.”
   • [claimed-docs] “useful for needs like CI/CD implementations, logging, creating user-agnostic webhooks, and other tasks that you normally wouldn't want gated…”
   • [claimed-docs] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account.”
   • [claimed-docs] “you can make requests on behalf of other users, and the requests themselves aren’t made using your personal Figma account”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   • [claimed-docs] “Create and manage [webhooks](/docs/rest-api/webhooks-endpoints/)”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files. For example: a collaborator comments on a file, or you add a new version…”
   • [claimed-docs] “useful for needs like CI/CD implementations, logging, creating user-agnostic webhooks, and other tasks that you normally wouldn't want gated…”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files.”
   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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
   Figma!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.figma.com/openapi.json, https://developers.figma.com/swagger.json, https://develo…”
   • [claimed-docs] “This gives you the ability to do things such as view and extract any objects or layers, and their properties from files, get usage data, or …”
   • [claimed-docs] “Leverage the power of our REST API to bring Figma into your external tools and products.”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 to Figma
   Figma~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   • [claimed-docs] “Create and manage [webhooks](/docs/rest-api/webhooks-endpoints/)”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files. For example: a collaborator comments on a file, or you add a new version…”
   • [claimed-docs] “Webhooks allow you to observe when specific events happen in files.”
   • [claimed-docs] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Figma
   Figma✓fullclaimed6/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Spline
   Figma~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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
   Figma!disputedcontradicted3/10

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

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

   proof ↗⚑ flag

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

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

   • [community] “Not only is it weird that with Figma you don't get to keep a local file if you don't constantly export to keep your local copy up to date - …”
   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”

   proof ↗⚑ flag

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

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

   • [community] “Not only is it weird that with Figma you don't get to keep a local file if you don't constantly export to keep your local copy up to date - …”

   proof ↗⚑ flag

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

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

   • [claimed-docs] “The Plugin API supports both read and write access to Figma's editors, allowing developers to view, create, and modify the contents of files…”
   • [claimed-docs] “The Plugin API supports both **read** and **write** access to Figma's editors, allowing developers to view, create, and modify the contents …”
   • [claimed-docs] “You can build plugins that run immediately when invoked by the user, or that require users to input information via custom UI.”
   • [claimed-docs] “allowing developers to view, create, and modify the contents of files”
   • [claimed-docs] “Create private plugins and widgets to keep internal information and data safe.”
   • [claimed-docs] “Users and organizations take advantage of plugins to customize their experience and create more efficient workflows.”
   • [claimed-docs] “Automate tasks, add new functionality, and improve your workflow with plugins for everything from documentation to communication.”
   • [claimed-docs] “Unlike plugins that run for a specific person, everyone can see and interact with the same widget.”
   • [claimed-docs] “This repository contains the OpenAPI specification and Typescript types for the Figma REST API”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Figma
   Figma✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   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 to Figma
   Figma~partialclaimed2/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   • [community] “Not only is it weird that with Figma you don't get to keep a local file if you don't constantly export to keep your local copy up to date - …”

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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