Part of Audit and Remediate Design Systems in Figma
Product & Design Blueprint
Audit Design Systems Across 4 Layers
Programmatic analysis of Figma design systems across technical soundness, UX quality, accessibility, and design intentionality.
What problem does this solve?
Analyzes your entire Figma design system (or a single component) across 4 audit layers: technical (tokens, color, typography, design-code drift), UX quality (touch targets, motion and feedback), accessibility (WCAG 2.2 AA/AAA), and design intentionality (aesthetic POV, documentation). It parses every page, component set, variant, variable, and style; compares against your codebase if provided; and surfaces every gap with concrete evidence from the actual Figma data, not assumptions.
How does it work?
Run the skill on your Figma file (or point to a single component). It reads your Figma structure programmatically, checking tokens, variables, component variants, styles, and (if you provide a codebase path) comparing token values against tailwind.config.js or tokens.json. The skill produces two outputs: a human-readable report with maturity scoring and a prioritized action plan, plus a machine-readable JSON with structured findings, missing inventory, design-code drift, and step-by-step fixes. If a previous audit exists, it diffs against the current state to flag regressions and improvements.
Included Skills
No skills in this group
What's required to run this?
Reads Figma programmatically via the Figma MCP, parsing variable collections (primitive → semantic → component token hierarchy), text styles, effect styles, component variant matrices, and naming conventions. For drift detection, requires access to tailwind.config.js or tokens.json in your codebase; compares token names and values to flag mismatches. Produces W3C Design Token JSON output. Audit snapshots versioned to audit-history/<date>.json for drift tracking.
Key Features
Dual Reporting
Human report with maturity score (0–5), shadcn/ui alignment, key risks, and action plan. Machine JSON with structured findings, missing inventory, and fix metadata.
Design-Code Drift Detection
Compares Figma token values against your codebase (tailwind.config.js, tokens.json) to flag divergences and identify the source of truth.
Regression Tracking
Diffs current audit against previous snapshots (stored in audit-history/) to surface improvements and regressions across runs.
Evidence-Based Findings
Every issue includes data from your actual Figma structure: hardcoded hex values, ALL_SCOPES pollution, missing variants, WCAG contrast failures, touch target violations.
Priority Ordering
Action plan ranked by lowest effort + highest impact, with effort/risk/impact fields for each fix.
About This Blueprint
- Industry
- Technology
More Blueprints to explore
Business Automation & Productivity Workflow
Reduce hours lost to repetitive admin without adding a complicated stack. Prioritized, tested workflows automate routine research, client communication, project tracking, and website tasks while keeping people in control of important decisions.
Business Technology & Digital Solutions Workflow
Avoid costly, fragmented digital projects with a plan that connects business goals to practical tools, implementation steps, and measurable results. It also flags performance, security, accessibility, and SEO checks before launch.
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