Skip to content

Product & Design Blueprint

Safety checked

Audit and Remediate Design Systems in Figma

0lsanchez-g2May 2026

A Claude Code skill that analyzes design systems across 4 audit layers (technical, UX quality, accessibility, design intentionality) and applies fixes directly in Figma.

Design System AuditingToken ManagementComponent ValidationAccessibility ReviewDesign-Code Drift Detection

Install Prompt

Copy this prompt and paste it into your AI agent to install.

What problem does this solve?

Audits your Figma design system programmatically across tokens, components, accessibility, and UX consistency, then applies fixes directly in Figma after your approval. It reads every page, variable, token, component variant, and style; compares design against code when a codebase is provided; flags gaps with evidence; and exports production-ready code artifacts (tokens, types, Storybook stories, documentation). The skill removes guesswork from design system governance by surfacing concrete issues with concrete fixes, not vague recommendations.

How does it work?

  1. Select your mode: Hardcore (full system audit), Soft (single component deep-dive), or Spec (validate against your custom requirements). 2. Provide your Figma file URL and (optional) your codebase path for drift detection. 3. The skill runs a 5-phase workflow: audit your Figma structure programmatically, produce a dual human report + machine JSON, wait for your approval on fixes, execute changes in Figma, export production code (tokens.json in W3C format, TypeScript types, Storybook stories, and HANDOFF.md documentation). Output: prioritized action plan, remediated Figma file, and drop-in code artifacts ready for your project.

Included Skill Groups

View Blueprint →

What's the biggest win?

Every design system gap surfaces with evidence and a fix, then gets applied directly to Figma and code, eliminating the back-and-forth between design and engineering.

What's required to run this?

Requires Claude Code (CLI or desktop app) because the skill executes as a Claude Code skill using the Figma MCP. Analyzes Figma's native variable scopes, text styles, effect styles, and component variant matrices without external dependencies. For drift detection, reads tailwind.config.js and tokens.json if a codebase path is provided, then compares Figma token values against code. Exports follow W3C Design Token format (Style Dictionary compatible) and generate Storybook stories in TypeScript with full variant coverage. All audit snapshots versioned to audit-history/ for regression tracking across runs.

What should I watch out for?

The skill requires Figma plugin support in Claude Code (installed via /plugin → figma) and edit access to your Figma file. Pixel fidelity on exports is ~97–99% due to renderer limitations (font anti-aliasing, corner smoothing). The v3 lossless extraction layer for round-trip Claude Design support is still in progress (Phases A–D complete by May 2026; Phase E queued for Sep 2026). Soft and Spec modes analyze a single component at a time, not the full system.

Key Features

3 Audit Modes

Hardcore (full system), Soft (single component), or Spec (custom requirements) — pick the scope that fits your workflow.

4-Layer Analysis

Technical (tokens, color, typography, drift), UX Quality (touch targets, motion), Accessibility (WCAG 2.2), Design Intentionality (aesthetic POV, documentation).

Evidence-Based Reporting

Human-readable report + machine-readable JSON with maturity scoring, design-code drift detection, and prioritized action plan.

Direct Figma Fixes

Apply approved changes directly in Figma with guaranteed backward compatibility and no visual regressions.

Production Code Exports

W3C Design Token JSON, TypeScript component types, Storybook stories for every variant, and HANDOFF.md system documentation.

Tools in this Blueprint

Claude logo
4.4(68 reviews)
Figma
Claude logo
4.6(456 reviews)
Figma MCP

About This Blueprint

License
MIT
Industry
Technology
Skills
0 workflows, 0 sub-skills, 1 standalone
2 Skills
Product & DesignSafety checked

Send Weekly Product Defect Reports

Catch product defects before scattered support tickets obscure a rising trend. Weekly reports group faults by product and type, compare them with the prior four weeks, and include customer photos and quotes for faster quality investigations.

Yuma AIYuma AIClaudeClaudeShopifyShopify

Urska Blagojevic

GTM Lead at Yuma AI (YC W23)

2 Skills
Customer ExperienceSafety checked

Fix Wrong AI Agent Answers Before They Recur

Stop the same support mistake from frustrating customers again: trace incorrect Yuma replies to the Handbook, missing order data, failed actions, or bugs, then test a proposed fix before publishing it. A weekly report highlights recurring causes and the next tickets to investigate.

Yuma AIYuma AIShopifyShopifyClaudeClaude

Urska Blagojevic

GTM Lead at Yuma AI (YC W23)

1 File
Customer ExperienceSafety checked

Onboard a new agency client in Hive from a project template

Avoid a client’s first week starting with unowned tasks or a missing kickoff. The setup shifts template dates, flags weekend deadlines and open owners, then verifies approved updates in Hive before handing over a week-one list and welcome-note draft.

HiveHiveClaudeClaude