How this skill is triggered — by the user, by Claude, or both
Slash command
/figma-to-code:audit-componentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Resolve Params**:
Resolve Params:
devServerURL: from Team Lead or $ARGUMENTSOn receiving nodeId from Team Lead or $ARGUMENTS:
Get Node-Level Screenshots:
get_screenshot with nodeId to get node-level screenshotbrowser_navigate to devServerURL if not already therebrowser_snapshot to get the accessibility tree[data-node-id="{nodeId}"] in the snapshot, extract the corresponding refbrowser_take_screenshot with this ref to get node-level screenshot, save to .playwright-mcp directoryref in subsequent checksVisual Check:
Style Check:
get_design_context with nodeId to get design context
browser_evaluate to run getComputedStyle() on data-node-id="{nodeId}" element to get implementation context
Compare with tolerance:
| Property | Tolerance |
|---|---|
| display, flex-direction | exact |
| font-family, font-weight | exact |
| font-size | +-1px |
| line-height | +-2px |
| color, background-color | exact match preferred, RGB channel delta <= 5 for rendering noise |
| opacity | +-0.05 |
| padding, margin, gap | +-2px |
| border-radius | +-1px |
| width, height | +-2px |
| box-shadow | visual match |
Interaction Check:
get_metadata with nodeId to check for interaction variants (hover, disabled, etc.)browser_hover on the refbrowser_take_screenshot with refbrowser_evaluate to check disabled/aria-disabled on the refbrowser_take_screenshot with refReport auditResult to the Team Lead:
nodeId: the node auditedscore: 1-10, overall fidelity between design and implementationpass: true if score >= 8issues: flat list of all issues, each includes:
category: visual | style | interactiondescription: what is wrong (e.g., font-size mismatch, icon missing, layout shift, etc.)expected: design value or expected behavioractual: implementation value or actual behaviorWait for next nodeId
npx claudepluginhub nonoroazoro/ai --plugin figma-to-codeUse when a backpressured loop has a front-end/UI change and needs to compare the rendered result against its design reference (a Figma frame or images on a Linear ticket) — catching layout, spacing, contrast, and visual-consistency defects automated tests and happy-path clicking miss.
Validates visual and accessibility quality via Chrome DevTools – screenshots, contrast, touch targets, and mockup-vs-implement diff. Use /verify for logic checks.
Verifies UI changes after modifications via skeptical screenshot analysis: confirms goals achieved, WCAG accessibility, and design system compliance.