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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

   Figma does ship an official CLI (Code Connect CLI, documented at the quickstart guide) which is used to sync design system components in code with Figma and keep MCP-generated code consistent with the codebase — supporting agentic/CI-style workflows. However, the evidence pack gives no detail on CLI command surface, scripting for AI agents, or independent hands-on validation beyond its existence. Missing for 10: detailed CLI usage docs for AI-native/agentic workflows, examples of CLI use in automated/agent pipelines, independent corroboration of the CLI's capabilities.

   • [probe] “official CLI documented at https://developers.figma.com/docs/code-connect/quickstart-guide/”
   • [github] “Figma's Dev Mode will display true-to-production code snippets from your design system instead of autogenerated code examples.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma.”
   • [github] “Code Connect is a tool for connecting your design system components in code with your design system in Figma. When using Code Connect, Figma…”
   • [claimed-docs] “Code Connect keeps your generated code consistent with your codebase.”

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

   ⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

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

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

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

   proof ↗⚑ flag

   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