Claude Design 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 Spline
   Claude Design~partialprobed4/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Spline
   Claude Design~partialcommunity5/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Claude Design
   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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

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

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

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

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

   proof ↗⚑ flag

   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

4. ai-native userBuild against official SDKs

   weight 2 · round to Spline
   Claude Design—none0/10

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

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

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Spline
   Claude Design—none0/10

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

   ⚑ flag

   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 Claude Design
   Claude Design✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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 drawn
   Claude Design✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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 userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Claude Design—none0/10

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

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

   proof ↗⚑ flag

   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

Ai

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

   weight 1 · round drawn
   Claude Design~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 userVersion, review, and roll back my automations

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

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

   ⚑ flag

   Spline~partialclaimed5/10

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

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

   proof ↗⚑ flag

Collaboration

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

   weight 2 · round to Spline
   Claude Design~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Spline
   Claude Design~partialclaimed4/10

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

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

   proof ↗⚑ flag

   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 Claude Design
   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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
   Claude Design!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   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

Plugins

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

   weight 2 · round drawn
   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Spline
   Claude Design~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Spline~partialclaimed6/10

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

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

   proof ↗⚑ flag

Canvas

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

   weight 2 · round drawn
   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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 Claude Design
   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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. designerFull version history lets me name milestones, compare, and restore any earlier state of a file

   weight 2 · round to Spline
   Claude Design—none0/10

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

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

   proof ↗⚑ flag

   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