← ClaudeAtlas

figma-to-codelisted

Use when implementing a Figma design at pixel fidelity, auditing design-vs-code parity, or migrating many screens or a second breakpoint — and whenever a size, colour, radius or spacing value is about to be read off a screenshot, scaled from another breakpoint, or inferred from a sibling frame.
shivams07/figma-to-code · ★ 0 · AI & Automation · score 50
Install: claude install-skill shivams07/figma-to-code
# Measuring Figma Designs ## Overview A Figma file is **source data containing defects**, not a specification. Screenshots show you what a frame *looks like*; they cannot show you hidden nodes, tofu codepoints, stacked duplicates, impossible padding, or a blur that is actually a copy of a photograph. Those only appear in the CSS. **Core principle: measure every value, infer none, and record every place you deliberately don't match the file.** The output is two documents: a **CSS spec** (the authority for how it looks) and a **deviations register** (every place the file is defective and what ships instead). Without the second document, "pixel-perfect" silently means "faithfully reproduced the bugs". ## When to Use - Implementing a Figma screen where fidelity matters - Auditing whether shipped code matches the design - Migrating a flow, a role, or a whole app from a redesign - Adding a second breakpoint from a different Figma file or page - Any time you catch yourself about to write a number you did not measure **Not for:** one screen you'll eyeball, or design work where the Figma file is a sketch rather than a spec. ## The Iron Rules Each of these exists because violating it produced a wrong answer that survived until something else contradicted it. 1. **Screenshots establish composition. Never values.** Use them to learn what a screen *is* and what it *does*. Never to read a size, colour, spacing, radius, or a background mechanism. 2. **Every value comes from `ge