storybook-figma-audit

Audits Storybook stories and showcase tiles against Figma masters to produce a prioritized parity bug list.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill storybook-figma-audit-vilnacrm-org
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: storybook-figma-audit
Source: https://github.com/VilnaCRM-Org/claude-plugins/tree/main/plugins/react-frontend-sdlc/skills/storybook-figma-audit
Command: npx skills add https://github.com/VilnaCRM-Org/claude-plugins --skill storybook-figma-audit-vilnacrm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Component libraries and showcase boards drift from their Figma designs over time, and manually checking every story and state is slow and error-prone. This Skill sweeps the whole suite, separates broken behaviour from wrong pixels, and reports recurring root causes so one fix closes many findings. ## Core Features & Use Cases - Suite-wide parity sweep: Maps every story and showcase tile variant (breakpoints, hover, focus, error, disabled states) to its Figma frame and node id, then verifies spacing, geometry, colours, typography, and interactive behaviour against the design master. - Categorized, prioritized reporting: Classifies findings as functional, visual parity, micro-deviation, or verified-clean, prioritizes them, and outputs a table with Figma node ids, rendered-versus-spec values, severity, and screenshot evidence. - Root-cause analysis: Identifies recurring causes such as controlled components without handlers, static showcase props, and misplaced MUI slot overrides so one fix resolves multiple findings. - Use Case: Before a release, run the audit across your component library's Storybook to catch accumulated design drift, then hand the prioritized bug table to the team for triage. ## Quick Start Audit all Storybook stories and showcase tiles against their Figma masters and produce a categorized, prioritized parity bug report with screenshot evidence.

Frequently Asked Questions about storybook-figma-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Storybook components against Figma designs?▼

Map each story and showcase tile variant to its Figma frame and node id, then compare spacing, geometry, colours, typography, and interactive states using values read from Figma's inspect mode. Report findings as a table with rendered-versus-spec values and screenshot pairs.

What is the difference between a parity audit and visual regression testing?▼

A parity audit compares components against Figma design masters to find implementation-versus-design drift, while visual regression testing diffs screenshots between commits. The audit categorizes and prioritizes findings; the regression suite detects changes over time.

Can I run a Figma parity audit without Storybook?▼

Yes, partially. When the storybook capability is unavailable or the story build target is null, the audit runs over the running app's routes instead of stories, with the skip recorded as a note.

Why do Storybook stories show components that cannot be clicked?▼

A common root cause is a controlled component rendered with a static value and no change handler, making every click a no-op. Wrap the story in local state or give the component a default-value path.

When should I not use a suite-wide Figma parity audit?▼

Skip it when fixing a single component against its design, which is a single-component parity task, or when diffing pixels between commits, which belongs to the visual regression suite. It also requires a Figma reference and a story surface.