Canva vs Claude Design

Agent ops

1. ai-native userAn agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them

   weight 2 · round to Canva
   Canva✓fullprobed9/10

   Canva ships an official MCP server explicitly documented to let AI assistants create designs from text, edit existing designs via natural language, manage assets/brand kits, and export/resize outputs — a clear write-capable agent surface, corroborated by a dedicated MCP docs probe. This is backed further by the Connect APIs (write-capable REST API with OpenAPI/SDK generation) and Apps SDK for programmatic design manipulation. missing for 10: independent/hands-on third-party verification that the MCP write operations work reliably in practice.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   Canva✓fullprobed8/10

   Canva's Connect APIs and MCP server both provide documented programmatic export capability — the MCP server explicitly supports 'Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, etc.) and resize designs for different channels', and the Connect APIs allow creating/syncing designs and assets with OpenAPI-generated SDKs, confirmed via a live probe of the MCP docs. This directly satisfies an agent's need to render/export designs programmatically. Missing for 10: independent/hands-on confirmation of actual export calls succeeding (no third-party corroboration, only first-party docs), and the OpenAPI spec itself wasn't resolvable via direct probe.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design~partialprobed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Canva
   Canva~partialprobed6/10

   Canva has an official documented MCP server enabling AI assistants to search/retrieve designs, pages and folders, manage assets and brand kits, and export in multiple formats (PDF/PNG/JPG/etc.), which covers much of 'pulling real design context' for an agent to act on. However, the story's specific terms — frames, variables, component mappings — aren't explicitly evidenced, and there's no independent/hands-on confirmation that a coding agent can actually reconstruct implementation-level design context via this server. Missing for 10: explicit support for design variables, frame-level structural access, component-to-code mapping, and third-party corroboration of agent workflows.

   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design~partialcommunity5/10

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

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

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Canva
   Canva✓fullprobed8/10

   Canva confirms an accessible llms.txt file (HTTP 200) plus multiple scoped llms.txt files for sub-docs (e.g., scim/llms.txt, admin/llms.txt, audit-logs/llms.txt) and dedicated .md docs pages (mcp.md, connect.md, apps.md) explicitly structured for agent consumption. missing for 10: independent/third-party confirmation of an agent successfully using llms.txt to navigate docs, and a root-level single canonical llms.txt covering all products rather than fragmented per-section files.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.canva.dev/llms.txt # Canva Developers Documentation This file lists documentation for Canva product…”
   • [claimed-docs] “Use the SCIM API to automate the provisioning of Canva user accounts for your team.”
   • [claimed-docs] “The Canva Admin API lets you manage teams, groups, and users in a Canva organization.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”

   proof ↗⚑ flag

   Claude Design✓fullprobed7/10

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

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

   proof ↗⚑ flag

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

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

   All evidence describes Canva exposing an official MCP *server* so external AI assistants (Claude, ChatGPT, etc.) can call Canva's own design tools (canva-docs-5, canva-docs-28, canva-probe-4) — the opposite direction of the story, which asks whether Canva itself can act as an MCP client plugging into external MCP servers to use their tools. No evidence shows Canva consuming or configuring external MCP servers.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “If you're a user wanting to connect your personal AI assistant to Canva's AI Connector, see our Help Center”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round to Canva
   Canva~partialprobed5/10

   Canva does ship an official CLI, but it is scoped narrowly to creating and managing Canva Apps (the Apps SDK), not a general-purpose CLI for AI-native workflows like design generation, export, or automation via Connect APIs — those are exposed via APIs/MCP, not the CLI. missing for 10: evidence of CLI supporting broader AI-native tasks (design generation, bulk export, Connect API operations), independent/hands-on usage reports.

   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

   Claude Design—none0/10

   Evidence shows Claude Design integrates with Claude Code via slash commands (/design-sync, /design) and handoff bundles, but this is Claude Code's CLI, not an official CLI shipped by Claude Design itself; no standalone CLI for Claude Design is documented.

   • [claimed-docs] “Pull in your design system from Claude Code using /design-sync or work directly in Claude Code with /design.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”

   proof ↗⚑ flag

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

   weight 3 · round to Canva
   Canva✓fullprobed8/10

   Canva provides well-documented Connect APIs with an OpenAPI description for client SDK generation, plus Apps SDK, Admin API, SCIM API, and a first-party MCP server enabling AI assistants to drive Canva programmatically — directly matching an AI-native user's ability to drive the product via public API. Missing for 10: independent hands-on corroboration of API robustness/rate limits and a directly resolvable public OpenAPI file (probe found candidate OpenAPI endpoints 404, though docs claim one exists).

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to Canva
   Canva✓fullprobed8/10

   Canva provides official SDKs (Apps SDK, Connect APIs) plus an OpenAPI description enabling generated client SDKs in various languages, a CLI for app development, and an official MCP server for AI-native integration—covering the core of building against official SDKs. Missing for 10: independent/hands-on developer corroboration beyond first-party docs, and the openapi.json probe returned 404 suggesting the spec isn't trivially discoverable at expected paths.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

Agentic features

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

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

   The evidence pack shows Canva letting users import external data to drive design generation, bulk creation, and personalized template population (canva-docs-7, canva-docs-8, canva-docs-32), but nothing shows Canva's AI analyzing a user's own data to surface insights or proactive suggestions (e.g., analytics-style recommendations). This is closer to data-driven content generation than 'AI-generated insights and suggestions from my data,' so there is no concrete evidence the described capability exists.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

   Claude Design~partialclaimed5/10

   Claude Design can pull in external data (Salesforce, QuickBooks, GitHub) and use it to generate on-brand designs, proposals, or campaign plans, which is a limited form of data-driven suggestion, but this is framed around design generation rather than analytical insight delivery, and no evidence shows dedicated 'insights/suggestions' features from uploaded datasets. missing for 10: dedicated data-analysis/insight generation UI, independent corroboration that it surfaces analytical insights (not just design outputs) from imported data.

   • [claimed-docs] “Turn this proposal into a one-pager a prospect will want to open. Pull their details from Salesforce and export it as a PDF.”
   • [claimed-docs] “Dig into your numbers in Intuit QuickBooks, plan a promotion to get sales up, generate branded assets in Canva, and get your next campaign s…”
   • [claimed-docs] “Import from GitHub, design files, or your local codebase so Claude can build with your real components.”
   • [claimed-docs] “Import from your codebase, a web capture, or DOCX, PPTX, and XLSX files.”

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   Canva~partialclaimed4/10

   Canva provides integration surfaces (Connect APIs, Apps SDK, Bulk create, Brand Template autofill, MCP server) that let developers or AI assistants trigger Canva actions programmatically, but these are all invoked by an external caller rather than being a built-in autonomous scheduler or background automation engine within Canva itself. Missing for 10: evidence of native scheduled/triggered automations, event-driven workflows, or an 'autopilot' feature that runs without external initiation.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

   Claude Design—none0/10

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

   ⚑ flag

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

   weight 3 · round to Claude Design
   Canva~partialclaimed3/10

   Evidence mentions a 'Canva AI' feature only in passing (pasting links to add context to designs) but provides no detail on delegating broader tasks to a built-in assistant; most AI-related evidence instead describes the MCP server that lets *external* AI assistants control Canva, not an assistant embedded within Canva's own UI. missing for 10: documentation of an in-app AI assistant's task scope, examples of users delegating multi-step design tasks to it, and independent/hands-on confirmation of its capabilities.

   • [claimed-docs] “Bring content into Canva AI by pasting links from other platforms to design with more context.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

   Claude Design✓fullcommunity8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Canva✓fullprobed8/10

   Canva ships an official MCP server explicitly designed so AI assistants can operate Canva via natural language — supporting design generation, editing, discovery, asset/brand management, export, and comments through NL commands, and this is corroborated by a probe confirming the documented endpoint. This directly satisfies the AI-native natural-language operation story, though it relies on third-party AI clients rather than a native in-product NL interface. Missing for 10: independent/hands-on user reports of NL command reliability, and evidence of a first-party conversational interface within Canva itself.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design✓fullcommunity8/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Canva
   Canva✓fullprobed7/10

   Canva's developer docs explicitly state it provides an OpenAPI description of the Connect APIs that can be used with code-generation libraries to produce client SDKs, directly matching the story. Confidence is tempered because the probe couldn't locate the actual spec file at common guessed paths (only generic /openapi.json etc. were tried, not the real documented location), so independent verification of downloadability is thin. Missing for 10: a probed/verified working download URL for the OpenAPI file and independent (non-vendor) confirmation it's actually fetchable.

   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

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

   No evidence of a sandbox/test environment separate from production data; Canva's docs describe live APIs, MCP server, and Connect APIs but nothing about a sandbox mode, test accounts, or mock environment for safe experimentation.

   ⚑ flag

   Claude Design~partialclaimed5/10

   Claude Design's core workflow is prototyping (mockups, interactive prototypes) that are explicitly separate from production code — 'no PRs, no code review' before user-testing — which implies a sandbox-like separation from shipped/production systems. However, there is no explicit mention of a dedicated sandbox environment, test data isolation, or protection of 'production data' in a technical/backend sense; the framing is about design/code review gating rather than data safety. missing for 10: explicit sandbox/staging environment terminology, guarantees about not touching production data or backend systems, and independent confirmation of this isolation in practice.

   • [claimed-docs] “Turn a static mockup into a shareable, interactive prototype you can test with real people. No PRs, no code review.”
   • [claimed-docs] “Designers can turn static mockups into easily-shareable interactive prototypes to gather feedback and user-test, without code review or PRs.”
   • [claimed-docs] “When a design is ready to build, Claude packages everything into a handoff bundle that you can pass to Claude Code with a single instruction…”

   proof ↗⚑ flag

Ai

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

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

   The evidence pack only covers developer-facing surfaces (Apps SDK, Connect APIs, MCP server, Admin/SCIM/audit APIs) and never mentions Canva's native in-editor AI asset tools like Magic Media image generation, Magic Eraser/background removal, Magic Edit content-aware fill, or Magic Write copy suggestions used directly by a designer inside the editor. Missing for 10: any documentation of built-in Magic Studio-style tools (image generation, background removal, content-aware fill, copy suggestions) operating natively within the Canva editor UI.

   ⚑ flag

   Claude Design~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Canva~partialprobed6/10

   Canva's docs describe design generation and editing from natural language via its MCP server (canva-docs-17, canva-docs-18, canva-docs-28, canva-docs-33), which lets AI assistants create and modify designs from text descriptions and specifications, plus discovery, export, and asset management. However, this capability is delivered through an external MCP integration/AI connector rather than a native in-editor 'Magic Design'-style prompt feature, and there's no independent/hands-on evidence confirming quality of generated mockups. Missing for 10: first-party in-product documentation of native prompt-to-design (e.g., Magic Design) generation, independent hands-on verification of output quality, and confirmation this works without third-party AI tool setup.

   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation:** Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

   Claude Design~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   Canva✓fullclaimed7/10

   Canva explicitly supports bulk operations via Bulk Create with data import, personalized Brand Template population at scale, and Connect APIs to sync/create many designs/assets programmatically, plus MCP/API access for AI-native automation across many items. Missing for 10: independent/hands-on verification of scale limits, no explicit rate-limit or batch-size documentation, and no third-party confirmation of true 'many items' throughput.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

   Claude Design~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Canva—none0/10

   Evidence shows audit logs tracking user activity, but no documentation of versioning, review, or rollback specifically for automations (Connect API integrations, MCP workflows, or bulk create jobs). There's no mention of automation history, diffing, approval workflows, or reverting automated changes.

   • [claimed-docs] “Use audit logs to track changes made by your team in Canva.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”

   proof ↗⚑ flag

   Claude Design—none0/10

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

   ⚑ flag

Collaboration

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

   weight 2 · round to Canva
   Canva~partialclaimed5/10

   Evidence confirms Canva supports commenting on designs and even integrating comments into external workflows (canva-docs-9, canva-docs-22, canva-docs-37), implying in-file review is possible, but there is no direct documentation of @mentioning teammates or explicitly 'resolving' comment threads within the editor. missing for 10: explicit documentation of @mention functionality, thread resolution/closing feature, and any first-party or independent confirmation of the full in-app review workflow.

   • [claimed-docs] “Receive and reply to Canva comments from any platform and simplify team communication.”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   proof ↗⚑ flag

   Claude Design~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

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

   The evidence pack focuses entirely on developer APIs, SDKs, MCP servers, and admin/provisioning tools; there is no mention of real-time multi-user editing, live cursors, or simultaneous in-editor collaboration features that are core to this story.

   ⚑ flag

   Claude Design~partialclaimed4/10

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

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

   proof ↗⚑ flag

Design systems

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

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

   Canva's evidence covers Brand Templates, Apps SDK, Connect APIs, and MCP integrations, but nothing describes design tokens/variables (colors, spacing, typography) as reusable, mode-based theme objects applied programmatically across designs — Canva's brand kit concept is not documented as a token/variable system with theme modes.

   ⚑ flag

   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and Brand Templates but contains no mention of a component system with variants, per-instance overrides, or linked source instances (like Figma-style components). Brand Templates allow personalization but are not described as variant-based linked components. Missing for 10: any documentation of a component/variant system, linked instance overrides, or source-of-truth syncing mechanism for design elements.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   Canva~partialclaimed4/10

   Canva offers Brand Kits and Brand Templates that centralize on-brand assets/styles for teams to reuse across designs (canva-docs-15, canva-docs-7, canva-docs-20), which is the closest analog to a shared component library. However, there is no evidence of a true library-linking mechanism where edits to a source style/component automatically or optionally propagate updates to files that already used it, which is the core of the story. missing for 10: documentation of update propagation/versioning when a Brand Template or Brand Kit element changes, evidence of per-instance 'update available' notifications, independent confirmation of this workflow in practice.

   • [claimed-docs] “Make Brand Templates easily accessible, so teams can quickly create and edit on-brand designs.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”

   proof ↗⚑ flag

   Claude Design~partialclaimed3/10

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

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

   proof ↗⚑ flag

Handoff

1. developerDesigns map to production code — component-to-code mappings or direct design-to-code output I can actually ship

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

   Canva's developer docs cover Apps SDK, Connect APIs, MCP server, and CLI for building integrations, but none of the evidence describes design-to-code output or component-to-code mappings that map a Canva design to shippable UI code (e.g., React/CSS export) as design tools like Figma do.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

   Claude Design~partialcommunity7/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Canva—none0/10

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

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Canva
   Canva~partialclaimed5/10

   Canva offers substantial API surface (Connect APIs, Apps SDK, SCIM, Admin API, MCP server) covering design creation, editing, export, comments, and asset management, but this is a curated set of endpoints rather than full parity with the UI editor's rich manual design capabilities (e.g. free-form drag-and-drop editing, most granular design tools). No evidence confirms full UI-API parity; the docs describe specific supported operations, not a claim of complete equivalence. Missing for 10: explicit parity claim or evidence that every UI editing action (e.g. fine-grained manual layout, all effects/filters) is API-accessible, and independent verification of coverage limits.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”

   proof ↗⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Canva
   Canva~partialclaimed4/10

   Canva supports exporting individual designs in open, standard formats (PDF, PNG, JPG, PPTX, MP4) via both the Connect API and the MCP server, giving users a way to pull their design content out in interoperable formats. However there is no evidence of a comprehensive account-level data export (brand kits, comments, team assets, settings, history) or a documented 'export all my data' / account deletion-and-portability feature that would let an AI-native user fully leave with everything intact. missing for 10: bulk/account-wide data export, documented data portability or GDPR-style export tool, evidence of exporting non-design data (comments, brand assets, admin/audit data) in open formats.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   proof ↗⚑ flag

   Claude Design!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

Plugins

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

   weight 2 · round to Canva
   Canva~partialprobed6/10

   Canva has a real extensibility ecosystem: the Apps SDK/CLI for building apps, an Apps Marketplace for public distribution, and team-private app sharing — directly supporting icon/data/accessibility-style plugins built by third parties. However, evidence is entirely first-party docs describing the SDK/marketplace mechanics; there's no independent evidence of marketplace size, breadth of existing third-party plugins (icons, accessibility checkers, data fillers), or community adoption. Missing for 10: independent verification of marketplace scale/quality, concrete examples of third-party apps in categories named in the story, user reviews or hands-on discovery of the marketplace.

   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [claimed-docs] “You can then either distribute the app publicly via the Apps Marketplace, or share it privately with members of your team.”
   • [claimed-docs] “Make apps for your team and choose who can use them.”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “Team apps are created solely for a team using Canva, such as an app created to integrate into a specific system.”
   • [claimed-docs] “Learn how you can turn your app into a business.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

Pricing

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

   weight 1 · round drawn
   Canva—none0/10

   The evidence pack is entirely developer/API documentation (Connect APIs, Apps SDK, MCP, SCIM, Admin API) and contains no pricing page, plan comparison, seat-type breakdown, or AI-feature gating disclosure that a procurement-focused product manager would need. Only one mention ('Private integrations can only be used by your team on a Canva Enterprise plan') hints at plan gating but is far from a published pricing/tier matrix.

   • [claimed-docs] “Private integrations can only be used by your team on a Canva Enterprise plan.”

   proof ↗⚑ flag

   Claude Design—none0/10

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

   ⚑ flag

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

   weight 2 · round drawn
   Canva—none0/10

   The evidence pack is entirely developer/API-focused (Connect APIs, Apps SDK, MCP server, SCIM, audit logs, admin API) and contains nothing about the consumer free-tier editor, its feature set, or free collaboration capabilities; one entry even implies enterprise-only integrations. No evidence supports or refutes what the free tier includes for a designer doing real design work.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Canva—none0/10

   No evidence in the pack mentions data residency, regional storage options, or location controls for Canva data; documentation covers APIs, SDKs, audit logs, and provisioning but not data residency/region choice.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Canva—none0/10

   The evidence pack contains only Canva developer docs about APIs, SDKs, MCP servers, and admin/audit tools — nothing addresses AI training data usage policies or opt-out controls for user content. Missing for 10: any documentation on AI training data policy, opt-out settings, or privacy controls related to model training.

   ⚑ flag

   Claude Design—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Canva—none0/10

   Evidence covers audit logs, SCIM provisioning, and admin/team management APIs, but nothing addresses data retention policies or user-initiated data deletion controls for AI-native usage (e.g., MCP/AI connector data handling, deletion of AI-processed content, retention settings).

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Canva—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings for AI-native users; documentation covers APIs, SDKs, MCP server, audit logs, and provisioning but nothing about disabling telemetry collection.

   ⚑ flag

   Claude Design—none0/10

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

   ⚑ flag

1. designerPrototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product

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

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of interactive prototyping capabilities such as animated state transitions, conditional logic, variables, or scroll-triggered effects within Canva designs. This is a fair axis for a design tool to be judged on, but nothing in the pack shows Canva delivers it.

   ⚑ flag

   Claude Design~partialcommunity4/10

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

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

   proof ↗⚑ flag

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

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

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

   ⚑ flag

   Claude Design~partialcommunity4/10

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

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

   proof ↗⚑ flag

Canvas

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

   weight 2 · round drawn
   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and admin/integration tooling, but contains no mention of responsive frames, auto layout, constraints, or grid-based resizing behavior akin to real UI flex layouts within the design editor itself. Design resizing mentioned (canva-docs-6, canva-docs-16) refers to static output resizing to new fixed dimensions, not dynamic responsive layout behavior.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of pen/path tools, boolean operations, or precision alignment controls for vector editing. Canva is a template-driven design tool, so this axis is fair to ask, but nothing in the evidence supports professional vector-editing capability.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag

Files

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

   weight 2 · round to Canva
   Canva~partialclaimed4/10

   Canva's docs confirm multi-format export (PDF, PNG, JPG, PPTX, MP4) and automatic resizing to new dimensions/aspect ratios, covering the basic 'PNG, SVG, PDF, and more' export need, but there is no evidence of SVG export, per-layer export presets, or slice-based export controls akin to design-tool layer/slice workflows. missing for 10: SVG export support, per-layer export presets, and slice/scale export tooling.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Automatically create resized versions of designs in new dimensions, formats, or aspect ratios.”
   • [claimed-docs] “Canva Pro and above: Design resizing to new dimensions”

   proof ↗⚑ flag

   Claude Design~partialcommunity3/10

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

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

   proof ↗⚑ flag

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

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

   Evidence shows only APIs (Connect API, Apps SDK, MCP) and export formats (PDF/PNG/PPTX/etc.) for integration, but no documented open native design file format — Canva's underlying .canva design representation itself remains proprietary and undocumented; users must go through the vendor's own APIs/exports to get data out, not a portable open format usable in other tools without Canva's platform.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

   Claude Design~partialcommunity6/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and admin/audit features, but contains no mention of file version history, naming milestones, comparing versions, or restoring earlier states of a design.

   ⚑ flag

   Claude Design—none0/10

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

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

   proof ↗⚑ flag