Part of Audit Design Systems End to End
Product Blueprint
Audit Design Systems End to End
A unified Claude Code skill with three modes for design system validation.
What problem does this solve?
Gives your design system a complete technical and UX audit in one conversation. It connects to your Figma file, surfaces every gap with evidence, and after your approval, applies fixes directly into Figma then exports production-ready code artifacts.
How does it work?
Choose your mode based on scope. Hardcore Mode audits your entire Figma system across four layers (technical, UX, accessibility, design intentionality), produces a maturity score and action plan, and applies fixes after approval. Soft Mode does an 8-point deep-dive on a single component, checking variant completeness, token bindings, states, and interaction quality. Spec Mode validates a component against your custom requirements. After you approve fixes, the skill applies changes in Figma, saves audit snapshots for drift detection, then exports tokens (W3C format, Style Dictionary compatible), TypeScript types, Storybook stories with realistic data, and a system handbook. Output: design-system/ directory with tokens.json, component.stories.tsx, component.types.ts, and HANDOFF.md ready to drop into your codebase.
Included Skills
No skills in this group
What's required to run this?
Requires Claude Code (desktop or web) with Figma MCP plugin installed. Reads Figma structure via use_figma tool calls. If codebase path provided, parses tailwind.config.js, tokens.json, and Storybook stories to detect design-code drift. Generates W3C Design Token format (Style Dictionary compatible), CSS custom properties with light/dark mode support, and TypeScript with full JSDoc. All exports follow production standards: realistic data, every variant named, every prop documented.
Key Features
Hardcore Mode
Full-system 4-layer audit (tokens, components, UX patterns, accessibility) with system maturity scoring and prioritized action plan.
Soft Mode
8-point single-component deep-dive: variant completeness, state coverage, token bindings, accessibility, visual consistency, documentation, code connect status, design POV alignment.
Spec Mode
Custom requirement validation: capture your specs ('add loading state', 'all colors must use semantic tokens'), audit against them, then apply fixes.
Direct Figma Execution
After approval, applies fixes directly into your live Figma file via MCP: token remapping, variant creation, binding corrections, state additions.
Production Code Exports
W3C Design Tokens (tokens.json, tokens.css, tokens.ts, tailwind.tokens.js), TypeScript component types with JSDoc, Storybook stories with every variant×state, and system documentation (HANDOFF.md).
About This Blueprint
- Industry
- Technology
More Blueprints to explore
ICP-Filtered Outreach Lists from G2 Buyer Intent
Stop wasting rep time on weak intent signals and mismatched accounts. The workflow ranks ICP-fit buyers by readiness, finds the right contact, and supplies tailored outreach angles for the strongest opportunities.
Ishani D.
Account Manager at G2