More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Doppelgänger: design QA, build vs Figma frame

    1

    Puts your build next to its Figma frame, measures every difference in spacing, type, colour and shape with both values, then fixes the code using your tokens and checks again.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Doppelgänger: design QA, build vs Figma frame

    Doppelgänger: design QA, build vs Figma frame

    Example session with this skill installed

    Does my build match the design? Figma: https://www.figma.com/design/FILE/Night-Owl?node-id=1-7 and the build is running at http://localhost:8769/pricing.html (it's the pricing card). Fix whatever's off in the CSS, but leave the copy alone.

    • Read your context and instructions
    • Compiled the doppelg nger
    • Generated the app files

    Design QA: Night Owl card vs pricing.html

    Design: Night Owl card (Figma frame) ·

    Build: http://localhost:8769/pricing.html (.card) at 1440px ·

    Method: measured values from the Figma file and the rendered page ·

    Date: 2026-10-29 ·

    Checked with: Doppelgänger 1.0 by Figmatro

    We compared the Night Owl pricing card in Figma with the .card element on the built pricing page. It was close in structure, but a few things were off: the card had no border and 20px padding instead of 24px, the title was 2px too small, the description and button were the wrong shades, the feature list was spaced too loosely and the button corners were too tight. The design's "Compare plans" link isn't in the build, and the build has a "Most popular with night-shift teams" line the design doesn't. Counts: 3 obvious, 5 noticeable, 1 subtle; 1 missing, 1 extra; 1 wording to confirm. The frame is a card rather than a whole screen and we couldn't tell the width of the screen it sits in, so we captured at 1440px; the card is a fixed 360px wide, so this doesn't change its layout. 9 of 10 text layers matched (90%), and we checked every finding against the side-by-side image: none were false matches. The three padding findings from the script (top, left and right) are grouped below as one issue.

    Obvious

    1. The card has no border

    • Where: Night Owl card (Figma) · .card (build)
    • Figma: 1px #E4E4E7 inside border (color/border/subtle) · Build: none

    What's different: the design card has a thin light-grey outline on all four sides; the build relies on the shadow alone.

    Fix: add a 1px border. Figma includes the stroke in the layout, so content sits 25px in (24px padding + 1px border), which box-sizing: border-box gives you.

    /* before */
    .card { padding: 20px; background: #FFFFFF; }
    /* after */
    .card { padding: 24px; border: 1px solid #E4E4E7; /* color/border/subtle */ background: #FFFFFF; }
    

    2. Description text is #71717A, not #52525B

    • Where: Night Owl card / Top / Intro / Description (Figma) · p.desc (build)
    • Figma: #52525B (color/text/secondary) · Build: #71717A

    What's different: the description reads noticeably lighter than designed (ΔE 11.5). The build uses the same grey as "/ month".

    • Fix: .desc { color: #52525B; } (color/text/secondary; the project has no CSS token for it).

    3. Title is 22px, not 24px

    • Where: Night Owl card / Top / Intro / Header / Heading / Title (Figma) · h2 (build)
    • Figma: 24px Inter Bold, 32px line height · Build: 22px Inter Bold, 32px line height
    • What's different: "Night Owl" is 2px smaller than designed.
    • Fix: h2 { font-size: 24px; }

    Noticeable

    4. Card padding is 20px, not 24px

    • Where: Night Owl card (Figma, auto layout) · .card (build)

    Figma: padding 24px on all sides (space/card-padding), plus the 1px border from #1, so content starts 25px in ·

    Build: 20px, no border, so content starts 20px in

    What's different: everything inside the card (badge, title, price, description, ticks, button) sits 5px closer to the top, left and right edges than designed. This is one cause behind the top, left and right padding findings.

    • Fix: .card { padding: 24px; } together with the border from #1 (shown in #1's snippet).

    5. Button is #6366F1, not #4F46E5

    • Where: Night Owl card / Actions / Button/Primary (Figma) · button.cta (build)
    • Figma: #4F46E5 (color/action/primary) · Build: #6366F1

    What's different: the button is a lighter, softer indigo than designed (ΔE 9.7). The design uses the same colour for the Compare plans link.

    • Fix: .cta { background: #4F46E5; } (color/action/primary)

    6. Button corners are 6px, not 10px

    • Where: Night Owl card / Actions / Button/Primary (Figma) · button.cta (build)
    • Figma: 10px radius · Build: 6px
    • Fix: .cta { border-radius: 10px; }

    7. Feature list gap is 16px, not 12px

    • Where: Night Owl card / Top / Features (Figma, auto layout gap) · ul (build)
    • Figma: 12px between rows · Build: 16px
    • What's different: the three ticked features are spread out more than designed, 4px extra per row.
    • Fix: ul { gap: 12px; }

    8. Price line height is 44px, not 48px

    • Where: Night Owl card / Top / Intro / Header / Heading / Price / Amount (Figma) · .amount (build)
    • Figma: 40px Inter Bold, 48px line height · Build: 40px Inter Bold, 44px line height

    What's different: the "$12" line is 4px shorter, which pulls the title, price and description closer together (see knock-ons).

    • Fix: .amount { line-height: 48px; }

    Subtle

    9. Badge letter spacing is 0, not 0.5px

    • Where: Night Owl card / Top / Intro / Header / Badge / Label (Figma) · span.badge (build)
    • Figma: 0.5px · Build: 0px
    • What's different: "NEW" is slightly tighter than designed; the badge is about 1px narrower as a result.
    • Fix: .badge { letter-spacing: 0.5px; }

    Words to confirm

    Copy often changes after the design, so these aren't counted as defects. Which version is current?

    Night Owl card / Actions / Button/Primary / Label (button.cta): Figma "Start free trial" · Build "Start your free trial"

    Missing from the build

    Night Owl card / Actions / Compare link (text, "Compare plans", 14px Inter Regular, underlined, #4F46E5 / color/action/primary): should sit centred 12px below the button. In the build that spot holds the "Most popular with night-shift teams" line instead.

    Extra in the build

    p.popular ("Most popular with night-shift teams", 12px, #71717A): centred under the button. Not in the design. Check whether it was added on purpose, or whether it was meant to be the Compare plans link.

    Knock-on differences

    These follow from the issues above and should clear up once those are fixed.

    • Night Owl card: height 434px → 424px. Follows from #4, #7, #8 and the missing link.
    • Button/Primary: width 310px → 320px. Follows from #1 and #4.
    • Button/Primary: space below it to the card's bottom edge 57px → 48px. Follows from the missing link / extra line and #4.
    • Badge: width 50px → 48.9px. Follows from #9.
    • Title → price: gap 8px → 5px. Follows from #8.
    • Price → description: gap 12px → 9.5px. Follows from #8.

    Needs a human check

    Tick icons: both sides show a green check at 16×16, 8px from the label, but the design's icon colour sits on a vector inside the instance and wasn't read, so we couldn't confirm the build's #16A34A stroke and 2px stroke width match.

    Shadow softness: both have a shadow; the build's 0 4px 12px rgba(24,24,27,0.08) equals the design's 0px 4px 12px 0px #18181B14 by value, but the script only checks that a shadow is present, so the rendered look is worth a glance.

    Matched

    • Fonts: all 10 text layers use Inter, and Inter loaded in the browser.
    • Font sizes and weights: badge 12px Bold, price 40px Bold, "/ month" 16px Regular, description and features 14px Regular, button label 15px Bold.
    • Line heights: badge 16px, title 32px, "/ month" 24px, description 20px, features 20px, button label 20px.
    • Colours: card #FFFFFF, badge background #EEF2FF and text #4338CA, title and price #18181B, "/ month" #71717A, feature labels #27272A, button label #FFFFFF.
    • Card: 360px wide, 16px corners, shadow present.
    • Badge: 4px / 10px padding, pill corners; "NEW" shown in capitals in both.
    • Spacing: badge → title 16px, price "$12" → "/ month" 6px, description → features 20px, features → button 24px.
    • Ticks: 16×16, 8px from their labels. Button: 44px high.
    • Description wraps onto 2 lines in both.

    Not checked

    • Hover, focus and pressed states of the button and link: the frame shows only the default state.
    • Other breakpoints: the frame is one 360px card; we didn't know the parent screen's width and captured at 1440px.
    • Dark mode: the design is light only.
    • The page around the card (the grey stage behind it) isn't part of the frame.

    We compared one frame at one width in one state. Other breakpoints, states and real content can differ, so check those too.

    Want us to fix these in the code and check again? Want these as a CSV for your ticket tracker?


    Fixed and checked again

    You'd already said yes to fixing the CSS, so we fixed all nine style causes (#1–#9, including the subtle letter spacing, since you asked for whatever's off in the CSS) in site/pricing.html. The project has no CSS tokens, so we used the raw values and noted the Figma token names in this report. We left the copy alone.

    #Change in site/pricing.html
    1, 4.card: padding: 20px → 24px, added border: 1px solid #E4E4E7
    2.desc: color: #71717A → #52525B
    3h2: font-size: 22px → 24px
    5, 6.cta: background: #6366F1 → #4F46E5, border-radius: 6px → 10px
    7ul: gap: 16px → 12px
    8.amount: line-height: 44px → 48px
    9.badge: letter-spacing: 0 → 0.5px

    Before → after: 9 differences → 0 left (3 obvious, 5 noticeable, 1 subtle → none), at the same width and selector. Knock-ons dropped from 6 to 2.

    Still different, and waiting on your decision:

    • Words to confirm: the button says "Start your free trial"; Figma says "Start free trial".
    • Missing: the "Compare plans" link isn't built.
    • Extra: "Most popular with night-shift teams" sits where the link should be.

    Knock-ons from those: the card is 430px tall, not 434px, and the space under the button is 53px, not 57px, because the 16px-high "Most popular" line takes the place of the 20px-high link. These clear once the link/line question is settled.

    Nothing was committed, and nothing in Figma was changed.

    pricing.html

    ZIP · project files

    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

    Every build has a double in Figma. Doppelgänger puts the two side by side and finds where they differ: a gap that's 4px out, a grey one shade too light, a font that never loaded, a link that never got built. It measures, so every finding says "Figma: 24px, build: 20px", never "looks a bit off".

    How it works

    1. Ask Claude. Share a Figma frame link and the page that was built from it, live or on your dev server, and ask "does this match?".
    2. Doppelgänger measures both. It reads the frame's real values from Figma, opens the page at the frame's width, and matches the two up: text by its words, boxes and icons by where they sit.
    3. You get a report, causes first. Every difference is marked Obvious, Noticeable or Subtle, with both values and where to find it in Figma and in the code. A card that's shorter because its padding is smaller is one issue, not twelve.
    4. It fixes the code, if you want. In Claude Code, say yes and it changes the CSS using your tokens, then checks again: "9 differences → 0 left".

    What it checks

    • Spacing: padding and gaps, measured inside each container, so one change is one finding.
    • Type: font family (including fonts that silently failed to load), size, weight, line height, letter spacing, wrapping and decoration.
    • Colour: text, backgrounds and borders, compared the way your eye sees them, with the token the design uses.
    • Shape: corner radius, borders, shadows and sizes.
    • What's missing, and what's extra: a link that never got built, a line nobody designed, and when one has replaced the other.
    • Words: copy that changed since the design, listed for you to confirm, not "fixed".

    Every report ends with what we checked and matched, and what we didn't check, so silence never looks like a pass.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    Needs a Figma frame link and the Figma connector. Measuring a live page or dev server needs Claude Code with Node.js 18+ and a local Chromium (installed after asking). On claude.ai it compares a screenshot, so values are estimated. Things it can't measure, like a swapped icon or a different photo, go under "Needs a human check". It checks one frame against one page or element at a time.

    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 buying a skill.

    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 13 days ago

    Accounts
    Figma MCP
    Software
    Node.js 18+PlaywrightChromiumGit

    Figma access is read-only. Node.js is for live pages (Claude Code). Playwright and Chromium install on first use.

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access

    Allowed Hosts

    api.figma.com

    Terminal and Browser: in Claude Code, Doppelgänger opens your page in a local Chromium (Playwright) at the frame's width and measures it. Network access: only to install Playwright and Chromium from npm the first time, after asking. Read and Write files: to find where a value is set in your code and, only for the differences you approve, change it. It never commits or pushes. Capture files go in a .doppelganger folder. Figma: read-only, through the Figma connector. Nothing in Figma changes, and nothing is sent anywhere else.

    Listed13 days ago

    What's inside

    Frequently Asked Questions

    Overlays show you two pictures and leave the spotting to you. Doppelgänger reads the real values on both sides, so every difference comes with the Figma value, the built value and where to find it. Then, in Claude Code, it can fix the code and check again.

    It's built not to. Every difference comes from a measurement on both sides. Anything it can't measure, like a swapped icon or a different photo, goes under "Needs a human check".

    Not about the words. Copy often changes after the design, so different wording is listed under "Words to confirm", and it asks before changing any text.

    No. It only reads the frame. The design is the reference, so nothing in Figma changes.

    Yes. If your Figma layers use variables, the report names them, and fixes use the matching token or theme value in your code where there is one.

    New in Frontend & Web Apps