Skip to content
ProductArena

Design & Prototyping Arena

Figma vs Framer

Figma logo

Figma

Figma, Inc.

Arena30/100AGENT-READY54/100BUILT-IN AI22/100
MCP✓CLI~API✓
free-tier35/100 integrity
Framer logo

Framer

Framer B.V.

Arena19/100AGENT-READY18/100BUILT-IN AI52/100
MCP—CLI—API~
free-tier22/100 integrity

Figma wins · 28–10 (15 drawn)

Agent design — stories about agent design in this arenaAgent design

Stories about agent design in this arena

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
    Figmafullprobed9/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
    Framerfullclaimed8/10

    Framer documents a write-capable external agent connection (Claude Code, Cursor, Codex) that can create/update/delete CMS items and modify canvas/components, backed by branching for safe review, plus a plugin surface and Server API for programmatic site automation. Missing for 10: independent/hands-on verification of the external-agent write capability and no public OpenAPI/formal API schema was found by the probe.

    • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
    • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
    • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
    • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
    • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
    • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
    • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
    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
    Figmapartialprobed6/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
    Framernone0/10

    Evidence covers AI agents editing designs, CMS, and publishing via a Server API and external-agent connections, but nothing documents a programmatic render/export surface for screenshots, images, or production-format exports (no export/render API endpoints, and probes for OpenAPI specs all 404).

    • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
    • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
    • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
    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
    Figmafullprobed9/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
    Framerpartialclaimed7/10

    Framer explicitly markets a native 'External Agent' connection (explicitly positioned as replacing a separate MCP server) that gives coding agents like Claude Code, Cursor, and Codex direct access to canvas, components, CMS, and project context, including read/write CMS operations and branch-based change tracking. This closely matches the story's intent of pulling design context to implement changes, but the specific mention of 'screenshots' and 'variables' from the story isn't explicitly evidenced, and all evidence is first-party docs with no independent/hands-on corroboration of the external agent workflow. Missing for 10: explicit support for screenshots/variables extraction, independent developer confirmation of the external-agent integration working as described.

    • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
    • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
    • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
    • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
    • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
    • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
    • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
    proof ↗⚑ flag

Agenticness — how well agents can access and operate the productAgenticness

How well agents can access and operate the product

Agent access

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

    weight 2 · round drawn
    Figmafullprobed8/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
    Framerfullprobed8/10

    A direct probe confirms Framer serves a live llms.txt file (HTTP 200) with structured content describing the product and linking to migration/agent docs, and Framer's own docs explicitly reference this file's content, giving concrete first-party evidence an AI agent can be pointed at it. missing for 10: independent/third-party confirmation that agents successfully consume this llms.txt in practice, and broader agent-oriented doc coverage beyond this single file.

    • [probe] “PROBE llms.txt: HTTP 200 at https://www.framer.com/llms.txt # Framer > Framer is an AI website builder for designers and teams. Generate ed…”
    • [claimed-docs] “Switch to Framer](https://www.framer.com/switch/?md): Migration from another builder.”
    • [claimed-docs] “Framer allows you to host static files directly on your site or custom domain. This feature is available on the **Pro**, **Enterprise**, and…”
    proof ↗⚑ flag

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

    weight 2 · round to Figma
    Figmapartialclaimed5/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
    Framerpartialprobed3/10

    Framer advertises a Server API to 'automate publishing' and integrate with external products/agents, which implies some programmatic/headless control, but there is no documented CLI, headless mode, or CI-specific workflow, and probes show no OpenAPI/API spec is publicly discoverable (404s). Missing for 10: concrete CI/headless setup docs, API reference/spec, and evidence of automated pipeline usage beyond marketing blurbs.

    • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
    • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
    • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
    proof ↗⚑ flag

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

    weight 3 · round drawn
    Figmanone0/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
      Framernone0/10

      Framer explicitly states it does not use or require MCP: 'Framer doesn't require a separate MCP server... without manual MCP setup' (framer-docs-34). Its actual capability runs in the opposite direction — external agents like Claude Code/Cursor connect INTO Framer to use Framer's canvas/CMS as their tool, not Framer consuming external MCP servers' tools. No evidence exists of Framer acting as an MCP client that plugs in third-party MCP servers.

      • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
      • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
      • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
      proof ↗⚑ flag

    • ai-native userConnect an agent via an official MCP server

      weight 3 · round to Figma
      Figmafullprobed8/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
      Framernone0/10

      Framer explicitly states it does not offer an MCP server, instead providing a proprietary 'External Agent connection' as an alternative to MCP (framer-docs-34). Since the story specifically asks for an official MCP server, and Framer's own docs assert this is unnecessary and unsupported by design, there is no evidence of an actual MCP server implementation.

      • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
      proof ↗⚑ flag

    • ai-native userUse an official CLI

      weight 2 · round to Figma
      Figmapartialprobed5/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
      Framernone0/10

      Evidence shows Framer offers a Server API, plugins, and 'External Agent' connections for tools like Claude Code/Cursor/Codex, but nowhere does it mention an official Framer CLI tool for AI-native workflows.

        ⚑ flag

      • ai-native userDrive the product through a documented public API

        weight 3 · round to Figma
        Figmafullprobed9/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
        Framerpartialprobed6/10

        Framer documents a Server API for automation/publishing and CMS API access, and explicitly supports external AI agents (Claude Code, Cursor, Codex) reading/writing CMS collections via a documented connection flow (framer-docs-5,17,30,39,40,18,24,34). However, probes could not locate any formal API reference/spec (openapi.json/swagger 404s) or detailed endpoint documentation, and there's no independent/community corroboration of developers actually using the Server API. Missing for 10: a discoverable formal API reference/spec, authentication/rate-limit details, and independent developer testimonials confirming API usability.

        • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
        • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
        • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
        • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
        • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
        • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
        • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
        • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
        proof ↗⚑ flag

      • ai-native userIssue scoped/least-privilege API credentials for an agent

        weight 2 · round to Figma
        Figmapartialclaimed4/10

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

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

        Framer documents a Server API and an 'External Agent' connection that lets tools like Claude Code or Cursor read/write CMS data and canvas content, with branching as a safety net for undoing changes — but nothing describes issuing scoped, least-privilege, or permission-limited API credentials/tokens for agents. Missing for 10: any mention of API key scopes, granular permission levels, token expiration/rotation, or role-based credential issuance for agent access.

        • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
        • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
        • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
        • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
        • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
        • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
        proof ↗⚑ flag

      • ai-native userBuild against official SDKs

        weight 2 · round to Figma
        Figmafullprobed8/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
        Framerpartialprobed6/10

        Framer documents a Server API, plugin SDK, code components/overrides, and an external agent connection for building integrations against official interfaces, but there's no discoverable OpenAPI spec (probe found 404s across candidate paths) and no independent/hands-on developer corroboration of building against these SDKs. missing for 10: publicly discoverable API reference/OpenAPI spec, independent developer corroboration, SDK versioning/language support details.

        • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
        • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
        • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
        • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
        • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
        • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
        proof ↗⚑ flag

      • ai-native userSubscribe to events via webhooks

        weight 2 · round to Figma
        Figmafullclaimed7/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
        Framernone0/10

        Evidence covers Framer's Server API, external agent connections, and plugins, but there is no mention of webhooks or event subscription mechanisms anywhere in the docs or probes; OpenAPI probe also returned 404s with no webhook spec found.

          ⚑ flag

        Agentic features

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

          weight 2 · round to Framer
          Figmadisputedcontradicted5/10

          Figma documents an AI agent that generates design directions, diagrams, images, and searches files, and touts 'AI agents work in the same space with shared context' (figma-docs-17, figma-docs-34, figma-docs-51), which matches the story's intent of AI-generated insights/suggestions from the user's own design data. However, hands-on community feedback specifically contradicts this: 'the AI tools in FigJam are really bad and often broken' (figma-comm-8), while another user reports success summarizing notes into slides (figma-comm-9), giving mixed real-world evidence rather than a clean full delivery. Missing for 10: independent benchmarks or broader corroboration of AI insight quality/reliability across Figma (not just FigJam), and clearer documentation of insight-generation (vs. content-generation) use cases.

          • [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
          Framerpartialclaimed4/10

          Framer's AI agent can restructure and suggest layout changes based on generic 'conversion best practices' (framer-docs-31/38) and manages/organizes CMS data (framer-docs-8/46), which is adjacent to data-driven suggestions, but there is no evidence of the agent analyzing a user's actual site/traffic data to surface analytical insights (e.g., performance, SEO, or visitor-behavior insights) — it is generative/design assistance rather than data-insight generation. Missing for 10: evidence of analytics-based insight generation, data pattern analysis, or dashboards summarizing user's own data trends.

          • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
          • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ, and make sure every s…”
          • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
          • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”
          • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
          proof ↗⚑ flag

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

          weight 2 · round to Figma
          Figmapartialclaimed5/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
          Framerpartialclaimed4/10

          Framer offers a Server API to 'automate publishing' and lets external agents (Claude Code, Cursor, Codex) connect to read/write CMS and canvas content, which could be wired into autonomous workflows, but all documented agent interactions (framer-docs-6/7/26) are conversational/on-demand rather than scheduled or self-running background automations. There's no evidence of triggers, schedules, or persistent background jobs — only API/connection primitives a developer would need to build such automation themselves. missing for 10: evidence of scheduled/triggered background jobs, autonomous run history or logs, native workflow/automation builder distinct from on-demand AI agent editing.

          • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
          • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
          • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
          • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
          • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
          proof ↗⚑ flag

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

          weight 3 · round to Framer
          Figmadisputedcontradicted5/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
          Framerfullclaimed7/10

          Framer ships multiple built-in AI agents (design agent, CMS agent, AI website generator) that users can delegate tasks to directly inside the product via natural-language prompts (e.g. 'make responsive', 'switch to dark mode', CMS setup) as shown in framer-docs-6,7,8,26,42,43,44,45,46. Missing for 10: independent/hands-on user reports specifically validating the built-in AI assistant's reliability and quality (community evidence available only covers older, unrelated Framer features like animations).

          • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
          • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
          • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
          • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
          • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
          • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
          • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
          • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
          • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”
          proof ↗⚑ flag

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

          weight 2 · round to Framer
          Figmapartialcommunity5/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
          Framerfullclaimed8/10

          Framer's docs show extensive natural-language operation: the built-in AI agent creates pages/sections/copy from prompts, restyles sites ('switch to dark mode', 'use Fraunces/Inter'), reorganizes layouts, and makes sites responsive purely from described intent, plus a CMS agent and external-agent integration (Claude Code/Cursor/Codex) that reads/writes CMS and canvas content via natural language, with branch-based safety for changes. missing for 10: independent/hands-on third-party corroboration of the AI/CMS agent actually working as described (community evidence only covers older non-AI Framer features).

          • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
          • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
          • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
          • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
          • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
          • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
          • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
          • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
          • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
          • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
          • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
          • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
          • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
          • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
          proof ↗⚑ flag

        Api quality

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

          weight 2 · round drawn
          Figmanone0/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
          Framernone0/10

          Framer documents a Server API, Plugins API, and Code Components, but nothing shows an interactive API reference with runnable/try-it examples; probe evidence explicitly found no OpenAPI/swagger spec (404s at all candidate paths), suggesting no such interactive reference exists.

          • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
          • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
          • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
          proof ↗⚑ flag

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

          weight 2 · round to Figma
          Figmafullprobed8/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
          Framernone0/10

          Framer offers a Server API and llms.txt, but the probe explicitly found no OpenAPI/swagger spec at any standard location, and no docs mention a downloadable machine-readable API spec.

          • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
          • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
          • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
          proof ↗⚑ flag

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

          weight 1 · round to Framer
          Figmanone0/10

          No evidence of a sandbox/staging environment or test mode that isolates AI-native testing from production Figma data; all MCP/API/plugin docs describe operating directly on real files and production content. missing for 10: any mention of sandbox environments, test/staging Figma instances, mock data, or non-production testing modes for AI agent workflows.

            ⚑ flag
            Framerpartialclaimed6/10

            Framer offers staging environments on a framer.app domain and automatic branching so AI agent changes happen in isolation from the live/main project, which functions as a sandbox against production data (framer-docs-10, framer-docs-11, framer-docs-25, framer-docs-36). However, this is framed around publishing workflow rather than an explicit 'sandbox for AI testing' concept, and there's no independent/hands-on verification of how well this isolation holds up in practice. missing for 10: independent corroboration of branch/staging isolation, explicit documentation framing this as an AI-testing sandbox rather than a publishing safety net, and detail on whether CMS data changes by agents are also fully isolated from production before merge.

            • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”
            • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
            • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
            • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
            • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”
            proof ↗⚑ flag

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

            weight 2 · round to Figma
            Figmapartialclaimed3/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
            Framernone0/10

            No evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI specs returned 404s and the Server/Fetch API docs mention no versioning or deprecation terms.

            • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
            • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
            • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
            proof ↗⚑ flag

          Ai design — stories about ai design in this arenaAi design

          Stories about ai design in this arena

          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
            Figmapartialcommunity5/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
            Framerpartialclaimed3/10

            Framer's AI agent can generate pages, sections, copy, and visuals (framer-docs-6, framer-docs-26, framer-docs-42) and adjust layout/typography, which touches copy suggestions and some visual generation, but there is no evidence of dedicated asset-chore tools like image generation, background removal, or content-aware fill inside the editor. missing for 10: dedicated image generation tool, background removal feature, content-aware fill capability, hands-on/independent verification of these specific asset tools.

            • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
            • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
            • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
            • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
            proof ↗⚑ flag

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

            weight 2 · round to Framer
            Figmapartialcommunity6/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
            Framerfullclaimed8/10

            Framer's docs describe a native AI agent that generates editable pages, sections, copy, and visuals from prompts, with examples of full mockup edits (typography, grid layouts, brand colors, dark mode, responsive breakpoints, image-based starting points), and lets designers keep refining in canvas after generation. This directly matches the story of prompt-driven first drafts/layouts/mockups, though evidence is entirely vendor-sourced with no independent hands-on verification of AI-generation quality — missing for 10: independent/hands-on confirmation that generated designs are production-quality, and any documented limitations of the AI design agent.

            • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
            • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
            • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
            • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
            • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
            • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
            • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
            • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
            • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
            • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
            • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
            proof ↗⚑ flag

          Automation depth — how much of the product can run unattendedAutomation depth

          How much of the product can run unattended

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

            weight 2 · round to Framer
            Figmapartialcommunity5/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
            Framerpartialclaimed6/10

            Framer docs show AI-agent driven bulk operations such as site-wide typography/color/theme changes across all pages (framer-docs-19,27,37), CSV bulk import of CMS collections with row-level linking (framer-docs-9,21), and external agents able to create/update/delete many CMS items via API (framer-docs-18,24,35). This supports bulk operations across many items in CMS/design contexts, but there's no documentation of scale limits, batch API endpoints, or performance at large volumes. Missing for 10: explicit bulk/batch API documentation with scale guarantees, independent verification of bulk operations succeeding at scale, and rate-limit/performance details.

            • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
            • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
            • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
            • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
            • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
            • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
            • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
            • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
            proof ↗⚑ flag

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

            weight 3 · round to Figma
            Figmapartialclaimed4/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
            Framernone0/10

            Evidence shows Framer's API, plugins, and AI agents that can be manually invoked to modify a site, and an API to 'automate publishing,' but nothing describes a rule engine or event-trigger system where a user defines 'when X happens, do Y' automation. missing for 10: any event-trigger/rule definition mechanism, conditional logic, or workflow automation builder within Framer.

            • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
            • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
            • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
            proof ↗⚑ flag

          3. ai-native userSchedule recurring jobs or workflows

            weight 2 · round drawn
            Figmanone0/10

            No evidence of any scheduling, cron-like, or recurring job/workflow automation capability in Figma's docs, API, webhooks, or MCP server offerings — webhooks are event-triggered, not scheduled recurring jobs.

              ⚑ flag
              Framernone0/10

              Framer's evidence covers AI agents editing sites, CMS, publishing, plugins, and APIs, but there is no mention of scheduling recurring jobs, cron-like automation, or workflow triggers of any kind. Automate publishing via API is a manual/programmatic action, not a recurring scheduled job.

                ⚑ flag

              • ai-native userVersion, review, and roll back my automations

                weight 1 · round to Framer
                Figmapartialclaimed4/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
                Framerfullclaimed8/10

                Framer documents automatic version history with instant rollback, plus branching that isolates every external-agent change so it can be reviewed, undone, or merged — directly matching version/review/rollback for automations run by AI agents. Missing for 10: independent/hands-on confirmation of rollback and branch-merge workflows in practice, and detail on granular diff/review UI beyond marketing docs.

                • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
                • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
                • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
                • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
                • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
                • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”
                proof ↗⚑ flag

              Collaboration multiplayer — stories about collaboration multiplayer in this arenaCollaboration multiplayer

              Stories about collaboration multiplayer in this arena

              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
                Figmafullclaimed6/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
                Framernone0/10

                Evidence covers branching, version history, AI agents, CMS, and plugins, but nothing about in-file commenting, @mentions of teammates, or resolving comment threads for design review. Missing for 10: any mention of a commenting feature, mention/notification system, or thread resolution workflow.

                  ⚑ flag

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

                  weight 3 · round to Figma
                  Figmafullclaimed8/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
                  Framernone0/10

                  The evidence pack includes docs on branching, version history, and staging (framer-docs-11, framer-docs-47) but contains no mention of real-time multiplayer editing, live cursors, or instant sync between simultaneous editors — the actual claim in the story. Missing for 10: any documentation of live cursors, simultaneous multi-user canvas editing, or real-time presence indicators.

                    ⚑ flag

                  Components design systems — stories about components design systems in this arenaComponents design systems

                  Stories about components design systems in this arena

                  Design systems

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

                    weight 2 · round to Figma
                    Figmafullclaimed8/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
                    Framernone0/10

                    Evidence shows Framer's AI agent can restyle colors/typography/light-dark mode on request (framer-docs-27, framer-docs-37, framer-docs-19), but there is no documentation of an actual design-token or variables system with reusable modes/themes applied consistently across designs, akin to Figma variables. Missing for 10: token/variable definition, mode-based theme switching infrastructure, cross-file/theme propagation evidence.

                    • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
                    • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
                    • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
                    proof ↗⚑ flag

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

                    weight 3 · round drawn
                    Figmapartialclaimed3/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.

                    proof ↗⚑ flag
                    Framerpartialclaimed3/10

                    Evidence only touches tangentially on component reuse — Code Components with visual controls and Code Overrides (HOCs to modify Layer/Component properties) hint at reusable, overridable components, but nothing explicitly describes variants or per-instance overrides that stay linked to a master component/source as in a design-system workflow. Missing for 10: explicit documentation of component 'variants', proof that per-instance overrides remain linked/syncable to the source component, and any hands-on/community confirmation of this specific workflow.

                    • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
                    • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
                    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
                    Figmapartialclaimed5/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
                    Framernone0/10

                    Framer's evidence covers code components, plugins, branching, and CMS collections within a single project, but there is no documentation of a shared/team library mechanism that publishes components or styles across separate files or projects with controlled update propagation (the Figma-style library model). Missing for 10: any mention of a cross-project component/style library, library publishing workflow, or update-notification/accept-update mechanism.

                    • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
                    • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
                    • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
                    proof ↗⚑ flag

                  Dev handoff — stories about dev handoff in this arenaDev handoff

                  Stories about dev handoff in this arena

                  Handoff

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

                    weight 2 · round drawn
                    Figmapartialcommunity7/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
                    Framerpartialcommunity7/10

                    Framer supports genuine dev-facing code integration: Code Components (custom React components with visual controls), Code Overrides (HOCs), a Server API, and native external-agent access letting Claude Code/Cursor/Codex read/write the live project and CMS with branch-based review before merge. Community evidence corroborates that Framer's React-based model lets designers hand off working code to developers. However this is not a classic 'export design to code' pipeline (no Figma-style code export or OpenAPI-documented flow was found), and independent verification is thin/dated. missing for 10: independent hands-on proof of shipping exported production code, more recent community validation of the external-agent/dev handoff workflow.

                    • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
                    • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
                    • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
                    • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
                    • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
                    • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
                    • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”
                    proof ↗⚑ flag

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

                    weight 3 · round to Figma
                    Figmapartialcommunity5/10

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

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

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

                      ⚑ flag

                    Openness — open source, data portability, and self-hosting storiesOpenness

                    Open source, data portability, and self-hosting stories

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

                      weight 2 · round to Framer
                      Figmapartialprobed5/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
                      Framerpartialprobed6/10

                      Framer exposes a Server API, external-agent connections (Claude Code/Cursor/Codex) with read/write CMS access, branching for review, and a plugin system that covers many editor actions (framer-docs-5,17,18,24,34,35,36) — a real, substantive API surface for automation. But there's no evidence of full UI/API parity: no OpenAPI/spec discoverable (framer-probe-3 shows 404s across candidate spec paths), and the docs describe specific supported actions (CMS CRUD, canvas edits via agent, publishing) rather than a claim that literally everything achievable in the UI (e.g. fine-grained styling, animation editing, plugin marketplace management) is scriptable via API. Missing for 10: a documented comprehensive API/OpenAPI reference proving parity, explicit vendor claim of 'anything in UI = anything via API', and independent/hands-on verification of that parity.

                      • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
                      • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
                      • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
                      • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
                      • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
                      • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
                      • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
                      • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
                      proof ↗⚑ flag

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

                      weight 3 · round to Figma
                      Figmadisputedcontradicted3/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
                      Framernone0/10

                      Evidence shows Framer offers a Server API, CMS API, and CSV import for content, but nothing indicates the ability to export a full site (design, code, CMS data) into open, portable formats for migration away from Framer; only 'migrate to Framer' flows are documented, not exit/export paths.

                      • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
                      • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
                      • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
                      • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
                      proof ↗⚑ flag

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

                      weight 2 · round drawn
                      Figmanone0/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
                      Framernone0/10

                      Framer is closed-source proprietary SaaS; no evidence pack item mentions an open-license source availability, and this is a mainstream commercial product with no indication of open-sourcing its codebase.

                        ⚑ flag

                      • ai-native userSelf-host the core product

                        weight 3 · round drawn
                        Figmanone0/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
                        Framernone0/10

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

                          ⚑ flag

                        Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibility

                        Stories about plugins extensibility in this arena

                        Plugins

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

                          weight 2 · round to Figma
                          Figmafullclaimed8/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
                          Framerpartialclaimed6/10

                          Framer documents a Plugins API for building editor extensions (small apps that interact with the Editor/CMS, insert layers/images/code components) with a dedicated developer docs section, plus adjacent APIs like Code Components and Server API. However, the evidence pack doesn't show explicit TypeScript typings references or concrete code samples/SDK repo, and there's no distribution/marketplace mechanism described. missing for 10: explicit typings documentation, concrete code samples/starter templates, and a distribution/marketplace mechanism for sharing plugins.

                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
                          • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
                          • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
                          • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
                          proof ↗⚑ flag

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

                          weight 2 · round to Figma
                          Figmafullcommunity7/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
                          Framerpartialclaimed5/10

                          Framer's docs confirm a plugin system where developers build 'small apps' that can interact with the editor and CMS (inserting images, layers, code components, modifying canvas), which is the technical foundation for a plugin ecosystem. However, the evidence never mentions a marketplace, community size, or specific plugin categories like icon packs, data fillers, or accessibility checkers as the story asks. Missing for 10: evidence of an actual marketplace/directory, plugin discovery UX, and named example plugins matching icons/data/accessibility use cases.

                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
                          • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
                          • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
                          proof ↗⚑ flag

                        Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans

                        Plan structure and value — what each tier costs and what it unlocks

                        Pricing

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

                          weight 1 · round to Figma
                          Figmapartialclaimed5/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
                          Framernone0/10

                          The evidence pack contains no pricing page, plan tiers, seat types, or AI-feature gating details — only one mention that a static-file hosting feature is limited to Pro/Enterprise plans, which does not constitute published plan/seat/AI-gating clarity. No pricing comparison table or plan documentation is present anywhere in the pack.

                            ⚑ flag

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

                            weight 2 · round drawn
                            Figmanone0/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
                              Framernone0/10

                              The evidence pack contains no mention of Framer's free tier, its editor limitations, or free-tier collaboration features; all docs focus on AI agents, CMS, publishing, and plugins. No pricing or free-plan details are cited anywhere in the pack, so there is no basis to confirm the free tier supports real design work or collaboration.

                                ⚑ flag

                              Privacy posture — data-handling and privacy storiesPrivacy posture

                              Data-handling and privacy stories

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

                                weight 2 · round drawn
                                Figmanone0/10

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

                                  ⚑ flag
                                  Framernone0/10

                                  No evidence in the pack addresses data residency, region selection, or data storage location controls for Framer; all evidence concerns AI agents, CMS, plugins, and publishing features unrelated to data residency.

                                    ⚑ flag

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

                                    weight 3 · round drawn
                                    Figmanone0/10

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

                                      ⚑ flag
                                      Framernone0/10

                                      No evidence in the pack addresses data usage for AI training, opt-out controls, or any privacy policy statement regarding training data; all evidence concerns AI agent features, plugins, and site publishing.

                                        ⚑ flag

                                      • ai-native userControl data retention and deletion

                                        weight 2 · round drawn
                                        Figmanone0/10

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

                                          ⚑ flag
                                          Framernone0/10

                                          The evidence pack covers Framer's AI agent, plugins, API, CMS, and version control/branching features, but contains no mention of data retention policies, data deletion controls, or privacy/compliance settings for AI-native workflows. Missing for 10: any documentation on data retention periods, user-initiated data deletion, or privacy controls specific to AI agent interactions.

                                            ⚑ flag

                                          • ai-native userOpt out of telemetry and usage tracking

                                            weight 2 · round drawn
                                            Figmanone0/10

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

                                              ⚑ flag
                                              Framernone0/10

                                              No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Framer's AI features or platform; all documentation covers unrelated capabilities (agents, CMS, plugins, publishing).

                                                ⚑ flag

                                              Prototyping — stories about prototyping in this arenaPrototyping

                                              Stories about prototyping in this arena

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

                                                weight 1 · round to Figma
                                                Figmapartialclaimed5/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
                                                Framerdisputedcontradicted6/10

                                                Framer's docs and community evidence confirm rich prototyping behavior — animated menus, carousels, code overrides, data-driven components (docs-45, docs-32, comm-4, comm-5) — but hands-on reports document concrete failures that undercut the 'feels like the real product' promise: animations distort during size/geometry changes, performance is inconsistent (60fps then chugging) on the same device, and users found Framer 'falls through' vs alternatives like react-spring when chaining multiple interactive animated nodes (comm-6, comm-7, comm-9). Missing for 10: independent verification that these animation glitches are resolved, and evidence of robust variable/conditional-logic support beyond CMS data binding.

                                                • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
                                                • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
                                                • [claimed-docs] “Fetch Building API endpoints that designers can use on their Framer sites without code.”
                                                • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”
                                                • [community] “As a ux designer... this is quite an interesting tool if you design software. It gives a nice blend between design and code. Your prototypes…”
                                                • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
                                                • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
                                                • [community] “I feel react-spring is better suited for the job... tried them both with r3f, i think it's just about API design and framer starts to fall t…”
                                                proof ↗⚑ flag

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

                                                weight 2 · round to Figma
                                                Figmafullcommunity9/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
                                                Framerpartialcommunity4/10

                                                Evidence shows Framer supports animations/transitions (community: 'great for more advanced prototyping needs w/ animations/transitions', 'declarative approach to creating nice animations') and AI-driven interactive elements like 'sticky navbars, animated menus, interactive carousels' handled via prompts, but there is no explicit documentation of screen-to-screen click triggers or overlay linking (the core Figma-style prototyping flow), and community reports flag animation performance/rendering glitches that undercut confidence. missing for 10: explicit docs on multi-screen click triggers, overlay/modal linking, and independent confirmation of a smooth no-code prototyping flow.

                                                • [community] “Framer is great for more advanced prototyping needs w/ animations/transitions/etc, but Adobe XD is pretty good and fast for many needs, and …”
                                                • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
                                                • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
                                                • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
                                                proof ↗⚑ flag

                                              Vector editing — stories about vector editing in this arenaVector editing

                                              Stories about vector editing in this arena

                                              Canvas

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

                                                weight 2 · round to Framer
                                                Figmapartialclaimed2/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
                                                Framerpartialclaimed6/10

                                                Framer's docs describe breakpoint-based responsive adaptation ('adapts your layouts across breakpoints, adjusting stacks, type sizes, spacing, and image crops') and general layout refinement (breakpoints, spacing) via its AI agent and canvas, which implies auto-layout/stack-style responsive behavior. However, there's no explicit documentation of manual constraints or grid systems, and no independent/hands-on corroboration of responsive resizing quality. missing for 10: explicit docs on constraints/grid systems, independent verification of resize fidelity across breakpoints, non-AI-agent manual workflow evidence.

                                                • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
                                                • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
                                                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
                                                Figmapartialclaimed4/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
                                                Framernone0/10

                                                The evidence pack is entirely about Framer's AI agents, CMS, publishing, plugins, and developer API — nothing addresses classic vector tools like pen/path editing, boolean operations, or precise alignment guides. No documentation or community evidence confirms these professional vector-editing capabilities.

                                                  ⚑ flag

                                                Versioning export — stories about versioning export in this arenaVersioning export

                                                Stories about versioning export in this arena

                                                Files

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

                                                  weight 2 · round to Figma
                                                  Figmapartialcommunity4/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
                                                  Framernone0/10

                                                  Framer is a website-builder/publishing tool, not a design/prototyping tool with layer-based asset export; the evidence pack contains no mention of PNG/SVG/PDF export, per-layer presets, scales, or slices — these are Figma/Sketch-style export features absent from Framer's docs.

                                                    ⚑ flag

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

                                                    weight 1 · round drawn
                                                    Figmanone0/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
                                                    Framernone0/10

                                                    The evidence pack covers Framer's APIs, plugins, CMS, and AI agent integrations, but contains no mention of an open or documented native file format that would let designs be opened, edited, or version-controlled by external tools outside Framer's own editor/publishing pipeline. Version history, branching, and staging are all Framer-hosted features, not a portable file format.

                                                      ⚑ flag

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

                                                      weight 2 · round drawn
                                                      Figmanone0/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
                                                      Framernone0/10

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

                                                        ⚑ flag

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

                                                        weight 2 · round to Framer
                                                        Figmapartialclaimed3/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.

                                                        proof ↗⚑ flag
                                                        Framerpartialclaimed5/10

                                                        Framer's docs confirm automatic version history with one-click restore of any prior version (framer-docs-12, framer-docs-22) and branching to isolate changes (framer-docs-11, framer-docs-47), but there is no evidence of naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: named milestone/checkpoint labeling, version comparison/diff view, independent hands-on confirmation of restore workflow.

                                                        • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
                                                        • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
                                                        • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
                                                        • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”
                                                        proof ↗⚑ flag