Figma to React, Verified

    1

    Figma frame in, React + Tailwind components out, with a measured pixel-diff and SSIM score proving they match the design.

    $17

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Figma to React, Verified

    Example session with this skill installed

    Implement this Figma frame in our Next.js app with Tailwind v4: https://www.figma.com/design/AbC123/Marketing?node-id=412-1880 (the pricing section). Make it match the design.

    • Read your context and instructions
    • Compiled the figma to react
    • Generated the UI component

    Preflight: Next.js 15 · Tailwind v4 · TS. figma-proxy-mcp connected (get_figma_component, render_node_png, verify_render). Frame "Pricing / Desktop" (412:1880), frameWidth 1440.

    **Plan confirmed** (GATE 1): PricingSection -> PlanCard (3 variants via `tier` prop) -> FeatureRow, Badge, Button (reused from `components/ui`).
    **Theme** (GATE 2): added 6 tokens to `@theme` in `app/globals.css`; 1 collision kept (`--color-primary` existing #2563EB vs Figma #2F6BFF -> added as `--color-figma-primary`).
    

    Build (GATE 4): lint, typecheck and build pass.

    Verify loop (verify_render, scale 2, outDir .figma-verify/diff)

    iterationpixelDiffPctssimgate
    14.31%0.931GATE 5 first pass: PASS
    22.64%0.947GATE 6 final: FAIL
    31.38%0.962GATE 6 final: PASS

    Fixes between iterations (largest region first):

    • iter 1 -> 2: region {x: 96, y: 212, w: 1248, h: 48, type: "layout"}: card titles wrapped; line-height 28px -> 24px from the node's box
    • iter 2 -> 3: region {x: 520, y: 640, w: 400, h: 56, type: "color"}: renderColor #2563EB vs refColor #2F6BFF (colorDelta 9.8) -> highlighted plan CTA now uses bg-figma-primary

    Remaining deviations

    region (x, y, w, h)typecausestatus
    96, 300, 1248, 420text glyphs"Inter Display" not installed, fallback Interaccepted (add the font to remove it)

    Files: components/pricing/PricingSection.tsx, PlanCard.tsx, FeatureRow.tsx, index.ts, app/globals.css (theme), public/icons/check.svg.
    Report: .figma-verify/report.md · diff image: .figma-verify/diff/pricing-desktop.png
    Overall: PASS WITH DEVIATIONS

    globals.css

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Most Figma-to-code flows stop at "looks about right". This skill makes your agent prove it. Paste a Figma link with a node-id and the agent works through gated steps:

    1. Preflight on your stack (React, Next.js or Vite; Tailwind v3 or v4; TS or JS) and a reference render
    2. Summary first: reads the frame summary, so a huge JSON tree never lands in context
    3. Tokens merged into your Tailwind theme without overwriting what you already have
    4. Atomic components generated from auto-layout using explicit mapping rules
    5. Preview: a bundled script builds a self-contained preview
    6. Verify loop: compares the preview to Figma's own render in headless Chromium

    Gates are explicit: diff ≤ 5% and SSIM ≥ 0.92 on the first pass, diff ≤ 2% and SSIM ≥ 0.95 for the final. Each diff region type has a fix strategy, iterations are capped and the loop stops when progress stalls. You get a report listing every remaining deviation.

    What you get

    • SKILL.md: a gated workflow in 8 steps, from preflight to report, with pass/fail criteria at each gate
    • references/: data handling (summary-first, point-fetch limits, large frames), Figma → Tailwind/React mapping table, Tailwind v3/v4 theme and merge policy, diff-region diagnosis table, troubleshooting
    • scripts/make-preview.mjs: zero-dependency Node script that renders a component (via your project's esbuild, React and Tailwind CLI) or a built page into one self-contained HTML file for verification
    • templates/report.md: final verification report

    Requires

    • An agent that loads SKILL.md with MCP support (Claude Code, Cursor, Codex CLI, Gemini CLI, etc.)
    • Free open-source MCP server figma-proxy-mcp (MIT, https://github.com/Semmargl/figma-proxy-mcp), install: npx -y figma-proxy-mcp --stdio. The skill checks for it and explains the install
    • Figma personal access token with read-only file content scope, set as FIGMA_API_KEY for the server
    • Node.js 20+, Playwright Chromium (npx playwright install chromium), and a React project (Tailwind v3 or v4)

    Permissions / network

    • The skill and its script make no network calls
    • The MCP server contacts only api.figma.com and Figma's image CDN, and never writes to Figma
    • Headless Chromium fetches only the remote assets the preview still references, and the script warns about each one
    • Writes component files, theme additions and icons in your project, plus working files in .figma-verify/

    Missing or licensed fonts leave a small residual diff in text regions, which the report lists. Blend modes, layer blur and cropped image fills cannot always be reproduced exactly in CSS. Each run verifies one width per frame and only the states drawn in Figma. Components that need a router or data fetching need a small preview wrapper (documented).

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Requires

    Figma
    Node.js 20+
    Playwright with Chromium
    Figma Proxy MCP
    Figma personal access token
    React project with Tailwind v3 or v4
    playwright
    Node.js

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    api.figma.com

    File Scopes

    src/**
    app/**
    components/**
    .figma-verify/**

    Terminal runs the bundled make-preview.mjs and your project's lint/build. Network only through the figma-proxy-mcp server: api.figma.com and Figma's image CDN, read-only, never writes to Figma. FIGMA_API_KEY (read-only Figma token) is read by the MCP server. Headless Chromium loads the local preview (plus any remote assets it still references, with warnings). Writes components, theme additions and icons in your project, plus .figma-verify/.

    Listed1 day ago

    What's inside

    Frequently Asked Questions

    Yes. figma-proxy-mcp is free and open source (MIT). Install it with npx -y figma-proxy-mcp --stdio and give it a read-only Figma personal access token as FIGMA_API_KEY.

    No. The server only reads file content and renders through api.figma.com and Figma's image CDN. It never writes to Figma.

    No. Figma tokens are merged: existing keys are kept, new ones are added, and a name collision with a different value gets a prefixed name. You see the theme diff before it is applied.

    Iterations are capped at 3 per gate, and the loop stops when the diff stops improving. Remaining regions are marked needs-human in the report with coordinates and cause, for example a missing font.

    New in Frontend & Web Apps