Sketch vs Rive

Agent ops

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

   weight 2 · round drawn
   Sketch✓fullclaimed8/10

   Sketch documents multiple write-capable programmatic surfaces: an official JavaScript Plugin API for creating/modifying designs, sketchtool CLI, sketch:// URL scheme for workflow integration, and explicit MCP support letting any MCP-compatible AI client connect to Sketch, including AI features that build out whole frames/pages from a repo. This goes beyond read-only inspection (which is the separate developer-handoff feature) into actual design creation/modification via agent tooling. Missing for 10: independent hands-on verification that MCP tools can actually write/modify designs (evidence is vendor-only), and no detailed spec of exposed MCP tool actions.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive documents an MCP integration letting AI tools create/modify complex View Models, State Machines, Layouts, and Shapes directly in the Editor, plus RML (a text-based file format) explicitly designed so coding agents can build/modify Rive files programmatically, and a CLI for agent-driven generation. This goes beyond read-only access into genuine write-capable agent tooling. Missing for 10: independent/hands-on verification of the MCP tools working in practice and more detail on the write-scope limits of the MCP server.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Rive!disputedcontradicted4/10

   Rive's runtimes expose a documented programmatic Renderer interface (rive-gh-1/2/3) and RML lets code/agents construct .riv content (rive-docs-13/20/25), and export docs describe exporting to 'websites, mobile apps, games, videos' (rive-docs-7/8) — suggesting a programmatic render/export surface. However, hands-on community feedback directly contradicts image/video export capability: users report 'no way to export movie files' and ask 'can I export video assets with this!?' with no answer (rive-comm-3, rive-comm-10), indicating the actual exportable surface is limited to the .riv runtime format rather than screenshots/images/production video as the story requires. Missing for 10: documented API/CLI for agent-triggered screenshot or image/video export, and confirmation this gap has been resolved.

   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Rive~partialprobed5/10

   Rive documents an official MCP server connecting the Editor to AI tools, letting agents create/modify View Models (variable-like data), State Machines, Layouts, and Components (rive-docs-19, rive-docs-27, rive-docs-10, rive-docs-11). This covers some 'design context' elements (component mappings, variables via view models) but is framed as agents building/editing Rive content rather than pulling existing frames or screenshots for implementation elsewhere. Missing for 10: explicit screenshot/frame extraction capability, evidence of pulling existing design context (vs. generating new), and independent/hands-on confirmation of the MCP workflow.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Sketch
   Sketch✓fullprobed8/10

   Sketch actually publishes an llms.txt file that returns HTTP 200 and serves a structured docs index for agent consumption (getting-started, prototyping, developer-handoff, workspace docs), confirmed by both docs listing and a runtime probe. Missing for 10: no evidence of broader agent-oriented markdown mirrors (the /docs/.md probe 404s) or an OpenAPI/machine-readable schema beyond llms.txt.

   • [claimed-docs] “Learn how Single Sign-On (SSO) and SCIM provisioning work in Sketch, and find step-by-step guides to get set up.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://www.sketch.com/llms.txt # Sketch ## Docs - [Getting started](https://www.sketch.com/docs/getting-start…”
   • [probe] “PROBE runtime (recorded 2026-09-07): https://www.sketch.com/llms.txt served a full docs index ('# Sketch') for agent consumption, covering g…”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.sketch.com/docs/.md”

   proof ↗⚑ flag

   Rive✓fullprobed7/10

   Rive's docs are served in agent-friendly markdown (docs/*.md return 200) and explicitly point agents to a documentation index at https://rive.app/docs/llms.txt for full-site context, satisfying the 'point an agent at llms.txt or agent-oriented docs' story even though the conventional root-level /llms.txt path 404s. Missing for 10: direct confirmation that /docs/llms.txt itself loads and contains a complete index, and no independent (non-vendor) corroboration of an agent successfully using it.

   • [probe] “PROBE llms.txt: HTTP 404 at https://rive.app/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://rive.app/docs/getting-started/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch~partialcommunity5/10

   Sketch documents a command-line tool (`sketchtool`) for scripted asset creation and claims it can integrate 'into your workflows and server applications, on any platform,' which points at CI/headless automation use. However, this is only first-party doc language with no independent verification, and community evidence confirms Sketch itself is strictly Mac-native and the vendor has refused Windows/Linux support, undercutting the 'any platform' claim. Missing for 10: independent CI/automation examples or case studies, clarity on macOS-only runtime requirements for sketchtool, and confirmation of non-interactive/headless execution in real pipelines.

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [community] “It's not just their commitment to Desktop, but their commitment specifically to not move off MacOS where they have stated that they 'will no…”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Rive exposes open-source runtimes as libraries (rive-gh-1, rive-docs-21) and mentions a CLI for agent-driven generation and RML for text-based/coding-agent workflows (rive-docs-26, rive-docs-25, rive-docs-30), suggesting some scriptable/automatable path outside the interactive editor. However, there is no explicit documentation of headless rendering, CI pipeline integration, or automated test/build usage of the CLI or runtimes. Missing for 10: explicit headless/CI usage docs, CLI reference/flags, examples of automated pipeline integration, independent confirmation of non-interactive operation.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch—none0/10

   Evidence only shows Sketch acting as an MCP *server* that external AI clients (e.g. Claude, Cursor) can connect to and use Sketch's own tools (sketch-docs-18, sketch-docs-34) — the reverse of the story, which asks whether Sketch itself can plug in external MCP servers to consume their tools. No documentation or community evidence indicates Sketch can act as an MCP client consuming third-party tool servers.

   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”

   proof ↗⚑ flag

   Rive✓fullprobed7/10

   Rive documents a first-party MCP integration letting users connect the Rive Editor to AI tools via MCP so AI can perform tasks like creating View Models, State Machines, Layouts, and Shapes, confirmed by both docs and a dedicated probe. Missing for 10: independent/hands-on verification of the MCP integration working in practice and details on which MCP clients/servers are supported beyond the editor's own tools.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch✓fullclaimed7/10

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

   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive's docs explicitly describe an official MCP server that connects the Rive Editor to AI agents/tools, letting AI handle View Models, State Machines, Layouts, Shapes, etc., and this is confirmed via a dedicated docs page and probe. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice beyond first-party docs.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Sketch
   Sketch~partialclaimed6/10

   Sketch ships an official CLI, `sketchtool`, documented for asset creation and integration into workflows/server applications on any platform, which agentic/AI tools could invoke. However, there's no evidence this CLI is positioned or extended for AI-native agent workflows specifically (no mention of AI agents using sketchtool, no JSON/agent-friendly output specs, and MCP support is a separate non-CLI integration). Missing for 10: agent-oriented CLI documentation, examples of AI/agent usage of sketchtool, independent hands-on confirmation of its use in automated pipelines.

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Use the Sketch Plugin Manager `skpm` to publish a new plugin or an update of an existing one.”

   proof ↗⚑ flag

   Rive~partialclaimed3/10

   The Rive homepage claims users can 'let an agent generate them with the CLI' (rive-docs-26), indicating an official CLI exists for AI-agent workflows, but no other evidence pack item documents CLI installation, commands, or usage — most AI-agent tooling evidence instead centers on the MCP server and in-editor AI agent, not a standalone CLI. Missing for 10: dedicated CLI docs/reference, install instructions, command examples, and independent/hands-on corroboration of the CLI working.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive documents open-source runtime APIs (web, mobile, game engines) for loading and controlling animations programmatically (rive-docs-21, rive-gh-1, rive-docs-14/15), plus a text-based file format (RML) explicitly designed for coding agents and automated workflows (rive-docs-13, 20, 25, 30), and an official MCP server/AI agent integration for driving the Editor via AI tools (rive-docs-19, 27, rive-probe-4, rive-docs-9/18). Together these give an AI-native user multiple documented, agent-friendly ways to control the product beyond the GUI. Missing for 10: a formal REST/OpenAPI-style public API (probe shows 404s for openapi/swagger endpoints) and independent third-party corroboration of programmatic API usage.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Rive
   Sketch~partialprobed6/10

   Sketch publishes an official vanilla JavaScript API, a CLI (sketchtool), plugin manager (skpm), and a documented sketch:// URL scheme for integrating into workflows and server apps, which constitute genuine official SDKs/APIs. However, there's no OpenAPI spec, no REST API, and probes confirm no openapi.json exists; the AI-native story is mostly served via MCP connectivity rather than a broad official SDK ecosystem. Missing for 10: a formal REST/OpenAPI API, multi-language SDKs beyond JS, and independent developer corroboration of building production integrations against these SDKs.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Use the Sketch Plugin Manager `skpm` to publish a new plugin or an update of an existing one.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive documents open-source official runtimes (SDKs) for web, mobile, game engines, and other platforms, with a public GitHub repo (rive-runtime) implementing the loading/rendering API, plus explicit guidance on caching and using the same exported .riv file across supported runtimes. This directly satisfies 'build against official SDKs' for developers, including AI-native workflows via RML/MCP integration for programmatic file creation. Missing for 10: independent third-party corroboration of SDK quality/completeness across all listed platforms and more granular per-language SDK documentation (e.g., npm/Swift/Kotlin package specifics).

   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Sketch—none0/10

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

   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”

   proof ↗⚑ flag

   Rive—none0/10

   No evidence anywhere in the pack mentions webhooks, event subscriptions, or any push-notification API for Rive; the product is documented as a design/animation tool with editor, runtime, and MCP/AI-agent integrations, none of which reference webhook-based event delivery.

   ⚑ flag

Agentic features

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

   weight 2 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Rive—none0/10

   Rive's docs describe an AI agent, MCP integration, and CLI that generate animations/code when invoked by a user, but there is no evidence of scheduled, unattended, or continuously running background automations — all AI features described are user-triggered, session-based interactions within the Editor.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch~partialclaimed4/10

   Sketch.com/ai lists several AI-powered automation features (auto dark-mode conversion, palette generation from a photo, automatic layer renaming/sorting, context-aware placeholder text) that a user can invoke to offload discrete design tasks, which is a form of task delegation. However, these are framed as one-off automated tools rather than a conversational, built-in assistant that takes freeform instructions, and the closest thing to an 'assistant' (docs-16/18/34) actually describes connecting an *external* MCP-compatible AI client to Sketch, not a native in-app assistant. Missing for 10: evidence of a conversational/chat-style built-in assistant, evidence of multi-step task delegation beyond single-purpose generators, and independent hands-on confirmation of these AI features working as described.

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

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive documents a built-in AI agent inside the Editor that writes code, generates layouts, data models, view models, state machines, and animation, letting users delegate repetitive/complex tasks to it directly within the product. This is first-party documented with specific task examples, though there's no independent/hands-on corroboration of its real-world effectiveness. Missing for 10: independent verification of the AI agent's actual capability/reliability, more detail on scope/limits of delegation.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch~partialclaimed6/10

   Sketch documents AI features (auto dark-mode conversion, color palette generation, layer renaming, placeholder text replacement) and explicit MCP-client connectivity so 'any MCP-compatible AI client' can drive design tasks, implying natural-language-driven operation via an external agent. However there is no first-party evidence of an in-app chat/command interface where a user directly types natural-language instructions to Sketch itself — the AI capabilities are either fixed one-click features or routed through external MCP clients. Missing for 10: a native in-app natural-language command interface, hands-on/independent verification that MCP-driven natural-language commands actually work end-to-end.

   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “Switch light mode components for their dark mode counterparts — all without making a single manual swap.”
   • [claimed-docs] “Replace placeholder text across every layer with true-to-life, context-aware content. No more lorem ipsum.”
   • [claimed-docs] “Sort, rename, and align layers automatically. Wrangle icon sets, keep Libraries clean, and bring calm to chaotic files.”

   proof ↗⚑ flag

   Rive~partialprobed6/10

   Rive documents a built-in AI agent and MCP integration that let users describe tasks in natural language to generate ViewModels, state machines, layouts, and animation code, plus a CLI for agent-driven generation (rive-docs-9,10,18,19,26,27). However, this is entirely first-party documentation with no independent or hands-on confirmation that natural-language commands reliably drive the full editor experience, and community feedback focuses on pricing/licensing rather than the AI agent's real-world behavior. Missing for 10: independent/hands-on verification of the AI agent's natural-language command success, broader coverage beyond docs-based claims, and detail on command scope/limits.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Sketch
   Sketch~partialprobed3/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   While Rive has extensive documentation (runtime parameters, data binding, RML), there is no evidence of an interactive API reference with runnable/live code examples, and the OpenAPI probe returned 404s with no playground or sandbox mentioned.

   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   A direct probe for OpenAPI/swagger spec endpoints (openapi.json, swagger.json, etc.) returned 404 for all candidates, and no docs mention a machine-readable API spec being downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of any versioned API scheme or documented deprecation policy for Rive's runtimes, editor APIs, or MCP integration; OpenAPI probes returned 404s and no changelog/versioning docs are cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

Ai

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

   weight 1 · round to Sketch
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   Rive's AI agent/MCP tooling is focused on generating code, view models, state machines, layouts, and animation logic — not on image generation, background removal, content-aware fill, or copy suggestions for asset creation. No evidence names any of these specific asset-chore AI features; missing for 10: image generation, background removal, content-aware fill, copy/text suggestions.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

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

   Sketch's AI page describes narrow, tool-specific AI features (auto light/dark mode conversion, photo-to-palette, code-to-design 1:1 fidelity, placeholder text replacement, layer auto-organization, and MCP-client integration to 'recreate text styles, colors, UI components, and even entire pages') rather than an open natural-language prompt that a designer types to generate an original first-draft layout or mockup from scratch. This is closer to targeted AI utilities layered onto existing designs than a general prompt-to-mockup generator. Missing for 10: evidence of a text-box/chat interface where a designer types a free-form prompt (e.g. 'design a pricing page') and Sketch outputs an original layout/mockup, and any hands-on or independent verification of AI generation quality.

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

   proof ↗⚑ flag

   Rive~partialprobed6/10

   Rive documents an AI agent/MCP integration that generates View Models, State Machines, Layouts, Shapes and animation from prompts or via coding-agent workflows, and even an 'agent generate them with the CLI' claim on the homepage — this matches the story's spirit of prompt-driven first drafts. However, all evidence is first-party docs describing 'the first set of tools' as handling repetitive tasks rather than full end-to-end mockup generation, and there's no independent/hands-on corroboration of output quality. Missing for 10: independent or hands-on validation of AI-generated designs, clearer evidence of full mockup/layout generation (not just repetitive sub-tasks) from a single prompt.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Rive~partialclaimed6/10

   Rive documents an AI agent/MCP integration explicitly designed to let AI 'handle repetitive tasks, like creating complex View Models, State Machines with hundreds of states/layers, Layouts, Shapes, and more,' and RML provides a text-based file format enabling coding agents to script bulk edits outside the Editor. Components/instances also let one source change propagate across many instances. However, there's no independent/hands-on evidence of actual bulk-operation performance at scale, no documented API for batch scripting beyond RML/MCP, and no benchmarks or examples of large-scale bulk edits succeeding. Missing for 10: independent verification of bulk-task performance, concrete examples/benchmarks of large-scale batch operations, and a documented API/CLI for scripted bulk edits beyond the AI agent's stated purpose.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch—none0/10

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

   ⚑ flag

   Rive~partialclaimed4/10

   Rive's State Machines and data-binding docs imply event-driven behavior (inputs, user actions, and data changes automatically triggering animation/state updates), and its AI Agent/MCP tooling can generate these State Machines and scripting-based behaviors programmatically. However, there's no explicit documentation of a rule-authoring system (e.g., conditional 'if event then action' automation) framed for AI-native/automation use beyond interactive animation triggers. Missing for 10: explicit rule-definition API/interface for arbitrary automation, examples of AI-native users authoring trigger-action rules, and independent confirmation beyond first-party docs.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Use scripting to create custom interactions, procedural animation, and behaviors that go beyond the built-in tools.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Sketch~partialclaimed4/10

   Sketch offers document-level version history via 'starred versions' that lets you track changes, control which versions are visible/published, and effectively roll back to prior states, which could cover AI-generated design changes; but there is no evidence of a dedicated 'automation' concept (e.g., saved AI workflows/scripts) with its own versioning, diff/review, or rollback mechanism distinct from general document history. missing for 10: evidence of versioning/rollback specifically for AI-generated automations/workflows (not just document snapshots), a review/diff UI for AI changes, and any audit trail tied to MCP/AI actions.

   • [claimed-docs] “starring a version will publish any changes as a Library update. Any unstarred versions after that won’t become Library updates.”
   • [claimed-docs] “When you star a version in a Library document, anyone using that Library will receive a Library update.”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document's history, set which versions Viewers and Guests can see”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document’s history, set which versions Viewers and Guests can see, and contro…”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Rive's Revision History provides automatic tracking of changes, previewing of past revisions, and non-destructive rollback to prior versions of a file (rive-docs-12, rive-docs-17, rive-docs-29), which covers version/rollback for the design file itself. However, the story targets 'automations' (AI-agent/MCP-driven workflows), and there is no evidence of versioning, diffing, or review specifically for AI-generated scripts, MCP actions, or automation pipelines — only generic file revision history. Missing for 10: dedicated versioning/review/rollback for AI-agent or MCP-generated automations, audit trail of agent actions, diff/compare tooling, and any independent confirmation of this workflow in practice.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

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

   The evidence pack covers developer handoff, prototyping, symbols, versioning, plugins, and AI features, but contains no mention of in-file commenting, @mentions, or thread resolution—core to this collaboration story. Community notes even highlight Sketch's historical lag on real-time collaboration features versus competitors, but nothing confirms comment/mention/resolve functionality exists.

   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”

   proof ↗⚑ flag

   Rive—none0/10

   Evidence covers animation, data binding, revision history, AI/MCP tooling, and export, but there is no mention of commenting, @mentions, or thread resolution features in Rive's editor. Revision history tracks changes but is not a comment/review workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch—none0/10

   No evidence in the pack documents live-cursor or simultaneous real-time multiplayer editing in Sketch; the only related community comment explicitly notes that as of late 2020 Sketch still lacked real-time collaboration ('the ability to collaborate in real-time' was still 'soon'), and Figma is cited as having this as its 'killer USP' that Sketch lacks.

   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”
   • [community] “A browser-based version of Sketch would be huge - this is Figma's killer USP at the moment.”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Docs confirm multiple people can work on the same file simultaneously with all changes tracked in Revision History, implying some multiplayer support, but there is no mention of live cursors, presence indicators, or real-time instant sync mechanics that the story specifically asks for. Missing for 10: explicit live cursor/presence UI, real-time sync latency claims, independent hands-on confirmation of simultaneous editing experience.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

Design systems

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

   weight 2 · round to Sketch
   Sketch~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   Rive is an animation/interactive-graphics tool with components, data binding, and view models, but there is no evidence of a design-tokens/variables system (colors, spacing, typography) with modes/themes applied across designs — the closest concepts (components, data binding) address reusability and runtime data, not token/theme management. Missing for 10: token or variable definitions, theme/mode switching, cross-design application of shared style values.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   Sketch~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive's docs directly describe Components as reusable artboards where instances can be customized while changes to the source component propagate to all instances, matching the story's core requirement of variants/overrides linked to source. Missing for 10: no independent/hands-on corroboration of override behavior at scale, and no detail on variant-specific overrides beyond basic customization examples.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullcommunity7/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   Rive's docs describe components/instances reused within a single Rive file where changes to a source component propagate to instances (rive-docs-11, rive-docs-28), but there is no evidence of a shared-library system that publishes components/styles across separate files or projects with controlled update propagation, which is the core of this story. Missing for 10: cross-file/cross-project library publishing, subscribing to a library, and controlled update notifications when a source library changes.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

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

   Sketch's AI page claims direct frame-to-code generation with '1:1 visual fidelity' and MCP-based AI client integration, plus browser-based developer handoff for inspecting specs, which together approximate design-to-code output; however this is entirely first-party marketing with no independent hands-on verification of code quality, supported frameworks, or shippability. missing for 10: independent/community confirmation that generated code is production-ready, details on output format/frameworks, and evidence of real-world dev usage of this AI code feature.

   • [claimed-docs] “Take any frame in Sketch and build it out in code with 1:1 visual fidelity.”
   • [claimed-docs] “Point your AI client at a repo to recreate text styles, colors, UI components, and even entire pages inside Sketch.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch.”
   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser”
   • [claimed-docs] “any developer can grab the information they need for any part of a design, at any time... they won't even need the Mac app (or a Mac) as it …”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive's core value prop is explicitly design-to-shippable-runtime: 'No mockups, no prototypes, no handoff... What you build in the editor is what ships in your app, game, or website' (rive-docs-23), backed by real runtime libraries that load .riv files directly into apps/games/web (rive-gh-1, rive-docs-21), reusable components/instances (rive-docs-11, rive-docs-28), and RML text representation enabling coding-agent-driven file construction (rive-docs-13, rive-docs-25, rive-docs-30). This is a genuine direct design-to-production path rather than a code-generation handoff, and MCP/AI agent tooling further bridges design and code workflows (rive-docs-9, rive-docs-19, rive-docs-27). Missing for 10: independent developer case studies confirming the 'no handoff' claim holds up in large production codebases, and clearer detail on how designers' Rive files integrate with existing component libraries/design systems in code.

   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch~partialprobed5/10

   Sketch exposes a JavaScript plugin API, a CLI (sketchtool), a URL scheme, and MCP-based AI integrations for asset creation and design manipulation, showing meaningful programmatic access beyond the UI. However, there's no evidence of a comprehensive REST/public API covering all UI functions (e.g., prototyping links, sharing/versioning, symbol libraries, workspace permissions) — openapi probes 404'd and docs focus on plugin/CLI/AI hooks rather than full UI parity. missing for 10: a documented full REST/GraphQL API covering all UI actions, evidence that non-plugin workflows (sharing, prototyping, library publishing) are API-accessible, and independent confirmation of API completeness.

   • [claimed-docs] “Write a Sketch plugin in JavaScript. Take advantage of ES6, access macOS frameworks and use the Sketch APIs without learning Objective-C or …”
   • [claimed-docs] “Try the Sketch JavaScript API now, directly within Sketch.”
   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”
   • [claimed-docs] “Integrate Sketch into your workflows with the `sketch://` URL scheme.”
   • [claimed-docs] “Connect any MCP-compatible AI client you like to Sketch. There are no tokens to buy, no extra tiers, and no add-ons.”
   • [claimed-docs] “An official vanilla JavaScript API, fully supported between releases.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.sketch.com/openapi.json, https://www.sketch.com/swagger.json, https://www.sketch.com/api…”

   proof ↗⚑ flag

   Rive~partialprobed5/10

   Rive offers RML (text-based file format) and an MCP server that let AI/coding agents create View Models, State Machines, Layouts, and Shapes programmatically, plus open-source runtimes for playback/control — but the evidence pack does not confirm full parity with the Editor UI (e.g., no OpenAPI/REST API, no confirmation that timeline keyframing, revision history management, or component/instance authoring can be done entirely via API/CLI). missing for 10: a documented public REST/OpenAPI API surface, confirmation that all editor features (keyframe timelines, revision history, component instancing) are scriptable/API-accessible, and independent hands-on verification that AI/API workflows match UI capability.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch~partialcommunity4/10

   Sketch documents use the open `.sketch` format (a zipped JSON+binary archive) rather than a proprietary opaque format, which supports portability and third-party tooling/git integration per community reports. However, there's no evidence of a full account/workspace-level export tool for bulk data extraction (comments, version history, workspace settings) to enable a clean 'export everything and leave' migration. missing for 10: bulk workspace/account export feature, documented data-portability/migration guide, independent confirmation of successful full data export.

   • [claimed-docs] “Sketch stores documents in .sketch format, a zipped archive of JSON formatted data and binary data such as images.”
   • [claimed-docs] “Sketch stores documents in `.sketch` format, a zipped archive of JSON formatted data and binary data such as images.”
   • [community] “The file format is basically zipped json files, so there's a robust plugin ecosystem and you can do things like git integration pretty easil…”

   proof ↗⚑ flag

   Rive!disputedcontradicted4/10

   Rive documents an open, text-based file representation (RML/XML) and open-source runtimes, suggesting some data portability (rive-docs-13, rive-docs-20, rive-docs-25, rive-docs-21, rive-gh-1). However, community feedback directly contradicts a full 'export and leave' story: users report no way to export movie/video assets (rive-comm-3, rive-comm-10) and note the open-source license only covers a narrow rendering subset while the actual content-creation editor remains proprietary and subscription-locked (rive-comm-5, rive-comm-1, rive-comm-2), undermining claims of full open-format data portability. missing for 10: documented full-fidelity export to universal open formats (e.g. video/SVG/JSON), open-source editor or file-format spec, and independent confirmation that RML round-trips 100% of file data without proprietary lock-in.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   Sketch—none0/10

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

   ⚑ flag

   Rive~partialcommunity5/10

   Rive's runtimes are documented and confirmed on GitHub as open-source libraries (rive-docs-21, rive-gh-1, rive-gh-2), giving AI-native users real source access to the rendering/runtime layer, but community evidence notes the MIT license only covers a 'rendering abstraction layer, a subset of the Rive runtime' while the Editor itself (where files are authored) remains closed-source (rive-comm-5, rive-comm-1). missing for 10: full-product open license (editor/design tool source not published), independent confirmation of license file/terms, clarity on what runtime components are excluded from the OSS layer.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Sketch—none0/10

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

   ⚑ flag

   Rive—none0/10

   Rive's core product is the proprietary Editor (a SaaS/desktop app); only a subset of the runtime rendering layer is open-source (MIT), and community evidence explicitly notes the editor itself cannot be self-hosted and requires the hosted tool to author content. No docs or evidence describe self-hosting the Editor or backend service.

   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

Plugins

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

   weight 2 · round to Sketch
   Sketch✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of a documented editor plugin/extension API, typings, or samples for building third-party editor extensions; the evidence only covers runtimes, data binding, AI agent/MCP integration, and RML scripting, none of which document an extensibility API for building/distributing editor plugins.

   ⚑ flag

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

   weight 2 · round to Sketch
   Sketch~partialcommunity7/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of a plugin marketplace, third-party extension ecosystem, or add-ons like icon packs, data fillers, or accessibility checkers. The evidence only covers Rive's own built-in features (components, data binding, MCP/AI agent, RML) — none of which describe an external plugin/marketplace ecosystem. Missing for 10: any mention of a plugin API, extension marketplace, or third-party-built add-ons.

   ⚑ flag

Pricing

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

   weight 1 · round to Sketch
   Sketch~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   The evidence pack contains only product/docs content about Rive's features (animation, data binding, AI agent, MCP) and community discussion referencing informal price points ($25-$39/month) but no published pricing page, seat-type breakdown, tier comparison, or explicit AI-feature gating documentation.

   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

   The evidence pack only shows free access for developers to inspect/hand-off designs in a browser (no Mac needed) and a legacy 'no forced upgrade' licensing note, but there is no evidence of a free tier that lets a designer actually create/edit designs or collaborate in real time without a paid seat — Sketch is fundamentally a purchased desktop app for designers. Community notes even highlight it lacked real-time collaboration for years and requires a Mac/license to design at all.

   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free”
   • [claimed-docs] “You can invite developers to inspect designs in your Workspace for free — they won't even need the Mac app (or a Mac) as it all happens in a…”
   • [claimed-docs] “they won’t even need the Mac app (or a Mac) as it all happens in a web browser.”
   • [community] “Newer versions of Sketch open old files just fine, and licenses are valid for any version. Sketch licenses do not 'expire', you simply can't…”
   • [community] “You don't have to pay to keep using Sketch, as long as you're ok with not upgrading. Unlike Adobe creative cloud that stops functioning the …”
   • [community] “Sketch is great software, well built, but the fact that in late 2020 they still have to write 'And soon, the ability to collaborate in real-…”

   proof ↗⚑ flag

   Rive—none0/10

   No evidence describes what the free tier includes for editor/collaboration access; the only relevant community signal explicitly states that basic solo-dev animation work requires a paid subscription ($25-39/month), suggesting the free tier is not sufficient for real design work.

   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”
   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ 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 Rive
   Sketch~partialclaimed4/10

   Sketch's docs show interactive prototyping via hotspots/links, overlays, hover/press/toggle triggers, and scrolling areas, which cover some 'feel like the real product' interactions, but there is no evidence of animated transitions between states, conditional logic, or variables — capabilities competitors highlight for advanced prototyping. Missing for 10: animation/transition effects between artboards, conditional logic or variable-driven states, and any documented scroll-triggered animation beyond basic scrolling areas.

   • [claimed-docs] “Create links or Hotspots to navigate between different frames or trigger Overlays.”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work”
   • [claimed-docs] “With features like overlays, hover, press and toggle triggers, and scrolling areas, you can accurately show how your designs would work in t…”
   • [claimed-docs] “Show Overlays (e.g. menus, dropdowns or dialogs) that appear when you click, press or hover over another layer.”

   proof ↗⚑ flag

   Rive✓fullcommunity8/10

   Rive's docs explicitly describe building interactive experiences responding to user input, screen size, scrolling, and application state (rive-docs-4), state machines/timelines/keyframes (rive-docs-3), and real-time data binding so animations update live (rive-docs-5, rive-docs-15, rive-docs-22, rive-docs-24) — directly matching the story's states/conditions/variables/scroll-effect prototyping needs. Community evidence corroborates real-world adoption for production-grade interactive UI/UX work (rive-comm-4, rive-comm-7), and Rive's own positioning ('no mockups, no prototypes... the real thing', rive-docs-16/23) reflects this design intent. Missing for 10: independent hands-on verification specifically of scroll-triggered effects and variable/condition-driven prototypes beyond vendor docs.

   • [claimed-docs] “Bring your designs to life with timelines, keyframes, and smooth interpolation.”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Connect animations, text, colors, layouts, and other properties to real-time data.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “I've been pushing over the past six months or so for multiple clients... to adopt Rive over Lottie and other past solutions, as I think it's…”
   • [community] “Truthfully the program they have looks fantastic at empowering UI/UX designers to do more with games... the workflow of this tool is definit…”

   proof ↗⚑ flag

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

   weight 2 · round to Sketch
   Sketch✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Rive~partialclaimed5/10

   Rive's State Machines and interaction docs (rive-docs-4, rive-docs-22, rive-docs-24) support building input-driven, trigger/transition-based interactivity without code, and rive-docs-16/23 frame the tool as skipping separate 'prototype' handoff entirely. However there is no evidence of a Figma-style multi-screen/overlay prototyping paradigm (linking distinct screens, overlay layers, click-through flows across artboards) — Rive's interactivity is scoped to state machines within/across components rather than an explicit screen-flow prototyping mode. Missing for 10: evidence of multi-screen linking, overlay/modal wiring, and click-through flow prototyping across separate artboards/screens.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”

   proof ↗⚑ flag

Canvas

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

   weight 2 · round to Rive
   Sketch—none0/10

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

   ⚑ flag

   Rive~partialclaimed5/10

   Rive's docs repeatedly reference "responsive layouts" and building interfaces that respond to screen size (rive-docs-1, rive-docs-4, rive-docs-9, rive-docs-18, rive-docs-26), and the AI tooling explicitly generates "Layouts" as an artboard-level construct (rive-docs-10). However, no evidence details the specific mechanics of auto layout, constraints, or grid systems the way Figma-style tools describe them. Missing for 10: explicit documentation of constraint-based resizing rules, grid systems, or auto-layout algorithms, and independent/hands-on confirmation that layouts flex like real UI frameworks.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

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

   weight 3 · round to Sketch
   Sketch~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Rive!disputedcontradicted3/10

   Rive's docs market it as a full design-to-ship tool ('design, animate, and code in one place... no mockups, no prototypes, no handoff') and mention vector graphics and components, but there is no documentation of boolean operations, precise alignment/snapping tools, or advanced path editing. A hands-on community comment directly contradicts the 'professional vector tools' claim, calling the drawing toolset just 'a pen and a couple of basic shapes' and comparing inefficient pen-only workflows unfavorably to real illustration tools. missing for 10: boolean operations, alignment/snap tooling, path-editing depth, and any rebuttal to the community criticism of basic drawing tools.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “Looks kinda interesting but I am not gonna touch anything that thinks an acceptable set of drawing tools is 'pen and a couple of basic shape…”

   proof ↗⚑ flag

Files

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

   weight 2 · round to Sketch
   Sketch~partialclaimed3/10

   The pack only hints at asset export via the `sketchtool` CLI ("Create assets with a single command") and never documents the actual Export panel, per-layer presets, scale factors, or slice tooling explicitly. Missing for 10: documentation of PNG/SVG/PDF format options, per-layer export presets, scale multipliers, and slice creation UI/behavior.

   • [claimed-docs] “Create assets with a single command with the Sketch command-line interface `sketchtool`.”
   • [claimed-docs] “Integrate Sketch into your workflows and server applications, on any platform.”

   proof ↗⚑ flag

   Rive—none0/10

   Rive's documentation focuses on exporting .riv files for runtime playback across platforms (web, mobile, games) rather than static production assets like PNG/SVG/PDF with per-layer presets, scales, or slices; no such export presets are described anywhere in the evidence. Community feedback explicitly confirms this gap — one user complains 'it's so insane they don't offer any way to export movie files' and another asks 'can I export video assets with this!?' — indicating the tool lacks traditional multi-format asset export entirely.

   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   proof ↗⚑ flag

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

   weight 1 · round to Sketch
   Sketch~partialcommunity6/10

   Sketch documents its .sketch file format as a zipped archive of JSON and binary data (sketch-docs-23/47), and community evidence confirms this enables a plugin ecosystem and git-style tooling outside the vendor app (sketch-comm-14). However, this is not a formally published open spec/standard with versioned schema docs, and there's no independent tooling ecosystem comparable to open formats like SVG; the developer-handoff features are more about inspection than format portability. Missing for 10: a formal published format specification/schema documentation, third-party tools that read/write .sketch independent of Sketch's own SDK, and any standards-body or open-format commitment.

   • [claimed-docs] “Sketch stores documents in .sketch format, a zipped archive of JSON formatted data and binary data such as images.”
   • [claimed-docs] “Sketch stores documents in `.sketch` format, a zipped archive of JSON formatted data and binary data such as images.”
   • [community] “The file format is basically zipped json files, so there's a robust plugin ecosystem and you can do things like git integration pretty easil…”

   proof ↗⚑ flag

   Rive!disputedcontradicted4/10

   Rive documents RML (a text-based/XML representation of Rive files) and open-source runtimes that can load/parse .riv files (rive-docs-13/20/25/30, rive-gh-1/3), suggesting some portability outside the editor. However, community evidence directly disputes this: the open-source runtime is described as only a rendering/playback layer, and actually authoring or building Rive content still requires the proprietary, paid Rive Editor (rive-comm-5), undercutting claims of full format openness/portability. Missing for 10: a public, versioned .riv binary spec independent of RML, third-party tools that can author/edit .riv files without the vendor's editor, and confirmation that RML round-trips losslessly with the binary format.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Sketch—none0/10

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

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

   proof ↗⚑ flag

   Rive—none0/10

   Evidence shows only the rendering runtime is open-source (rive-docs-21, rive-gh-1/2/3), while the Editor itself is a hosted SaaS product requiring Rive's cloud service—there is no documentation of a self-hostable full design platform. Community discussion explicitly confirms this gap, noting the MIT license covers only 'a subset of the Rive runtime that requires the Rive Editor to build content for' (rive-comm-5), meaning the actual design/editing platform cannot be self-hosted.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   Sketch~partialclaimed5/10

   Sketch's docs describe 'starred versions' that let designers mark important updates in a document's history and control which versions become Library updates or are visible to Viewers/Guests, which covers naming/milestone-marking, but the evidence never describes a compare/diff view between versions or an explicit 'restore to any earlier state' UI. Missing for 10: documented version comparison/diff tooling, explicit restore-to-previous-version workflow, and any independent/hands-on confirmation of these version-history mechanics.

   • [claimed-docs] “starring a version will publish any changes as a Library update. Any unstarred versions after that won’t become Library updates.”
   • [claimed-docs] “When you star a version in a Library document, anyone using that Library will receive a Library update.”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document's history, set which versions Viewers and Guests can see”
   • [claimed-docs] “With starred versions, you can indicate important updates in a document’s history, set which versions Viewers and Guests can see, and contro…”

   proof ↗⚑ flag

   Rive~partialclaimed6/10

   Rive's docs confirm automatic revision tracking, non-destructive restore, and the ability to select and edit a prior revision (rive-docs-12, rive-docs-17, rive-docs-29), which covers 'restore any earlier state.' However there is no evidence of naming/labeling milestones or a compare/diff view between versions. Missing for 10: named milestone/labeling capability, side-by-side or diff comparison between revisions, independent corroboration of the restore workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag