figma-check-design-parity
Skill83 starsChanged 6 months agoMITView on GitHub
Compare a Figma node's actual specs against a code spec (the values your component renders) and get a 0–100 parity score, a list of discrepancies, and fix suggestions. Use to detect design-to-code DRIFT: triggers 'check design parity', 'does my code match the Figma', 'compare this component to the design', 'is my implementation faithful', 'find differences between design and code', 'verify the build matches Figma', 'design QA against code', 'parity score'. Reads the node's visual / typography / spacing / token / accessibility specs via use_figma (any plan) and diffs them against a codeSpec you provide. Complements the native get_design_context: instead of GENERATING code, it VALIDATES that existing code stayed in sync with the design.
In this repository22 other files it gives its agents.
- figjam-create-contentSkill
- figma-analyze-component-setSkill
- figma-annotationsSkill
- figma-arrange-component-setSkill
- figma-audit-accessibilitySkill
- figma-blame-nodeSkill
- figma-commentsSkill
- figma-component-propertiesSkill
- figma-deep-componentSkill
- figma-design-system-inventorySkill
- figma-export-tokensSkill
- figma-extract-design-systemSkill
- figma-generate-changelogSkill
- figma-generate-component-docSkill
- figma-import-tokensSkill
- figma-library-variablesSkill
- figma-lint-designSkill
- figma-manage-variablesSkill
- figma-scan-code-accessibilitySkill
- figma-setup-design-tokensSkill
- figma-slidesSkill
- figma-version-historySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
All design reads go through use_figma, so it works on any Figma plan.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
figma-check-design-parity — design vs code drift checker
Pull a Figma node's real specs and diff them against a codeSpec (what your implementation
actually renders). Returns a weighted parity score, per-property discrepancies with severity, and
suggested fixes. This is the inverse of code generation: get_design_context turns a design into
code; this skill confirms the code didn't drift away from the design.
All design reads go through use_figma, so it works on any Figma plan.
Skill boundaries
use_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat the top of each script, colors in 0–1 range, load fonts before any text op,await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).- Generating code from a design → that's the native
get_design_context; this skill validates, not generates. - CODE-side a11y to feed
codeSpec.accessibility→ usefigma-scan-code-accessibility(--map-to-codespecemits exactly that object). - Design-side WCAG lint → use
figma-lint-design.
Workflow
- Assemble the codeSpec. Gather the values your component renders into the
codeSpecobject (references/parity-scoring.md has the full shape). You only need to fill the sections you want compared —visual,spacing,typography,accessibility. Tip:figma-scan-code-accessibility --map-to-codespecbuildscodeSpec.accessibilityautomatically. - Read the design specs. Set
NODE_IDand paste yourcodeSpecintoscripts/check-parity.js. Run it viause_figma(skillNames: "figma-check-design-parity"). It extracts the node's fills, strokes, corner radius, opacity, padding/gap, and text properties, then diffs them against the codeSpec. - Read the scorecard.
summary.parityScoreismax(0, 100 − (critical×15 + major×8 + minor×3 + info×1)).discrepancies[]lists each mismatch withcategory,property,severity,designValue,codeValue, and asuggestion. - Decide which side to fix. Each discrepancy says what design has vs what code has. Update code to
match the design, or push the design to match an intentional code change (via
figma-manage-variables/figma-use), then re-run to confirm the score rose.
Key rules
- Colors are 0–1 in Figma; the script converts to hex and normalizes both sides before comparing.
- Only filled codeSpec sections are compared. Omit a section to skip it — no false positives for data you didn't provide.
- Numeric tolerance: dimensions compare with a small epsilon (≈2px for width/height, 0.01 for opacity) so sub-pixel rounding doesn't register as drift.
- Severity drives the score: color/spacing mismatches are
major(−8), radius/border-width/opacity areminor(−3). See parity-scoring.md for the full weighting.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

