Skip to content

Part of Inspect, Build, and Sync Figma Design Systems

Product & Design Blueprint

Inspect, Build, and Sync Figma Design Systems

0June 2026

A single skill that audits design system files, creates or extends components and tokens, and optionally exports them to code.

What problem does this solve?

Provides read-only audits and build capabilities for Figma design systems in a single skill with two modes. Inspect mode scores components across six weighted dimensions (token compliance, interactive states, WCAG compliance, detached instances, naming, descriptions) and always pauses before any changes. Build mode orchestrates a six-phase workflow to create or extend components, add slots, bind variables, write descriptions, validate, and optionally generate code exports. The skill eliminates the gap between design-to-code by keeping Figma structure and exported tokens, scripts, and rules synchronized.

How does it work?

Invoke with a request like 'audit my design system' or 'build a design system for fintech'. The skill auto-detects mode: inspect runs read-only audits and stops with a report; build proceeds through six phases with mandatory pauses between each for your review and confirmation. Within each phase, the skill validates changes before continuing. For code export, the skill reads your Figma variables via the Figma MCP and generates tokens.css, an audit script, and AI rules for your project root.

Included Skills

No skills in this group

What's required to run this?

Requires figma-use skill and Figma MCP server (remote recommended). LineHeight variables must store pixel values, not percentages. Every variable requires explicit scopes (not ALL_SCOPES) and codeSyntax.WEB set for CSS token name delivery to agents. Descriptions use plain text formatting (no markdown) to match Figma MCP delivery. Phase 6 requires file write access; in Claude.ai web outputs file contents inline for manual saving.

Key Features

Weighted audit scoring

Scores components 0–100 across token compliance (errors ×2, warnings ×0.6), interactive state coverage (×3), WCAG AA compliance (×1), detached instances, naming quality (×0.5), and description completeness.

Six-phase build workflow

Discovery (analyze sources), Foundations (variables and styles), File structure, Components with slots, Validation, and optional Phase 6 (code export). Pauses between phases.

Slots for compound components

Uses named slots instead of detach patterns for Card, Modal, Dialog. Prevents accidental detaching and keeps dropzones visible to agents.

Mandatory structured descriptions

Every public component requires PURPOSE, BEHAVIOR, COMPOSITION, USAGE, CODE NOTES. Figma MCP delivers these as context so agents understand intent.

Three-layer token indirection

Phase 6 generates tokens.css with Primitives, Semantic aliases with fallback, and Components reference aliases, so upstream changes ripple through one layer and fallbacks keep the project running.

About This Blueprint

Industry
Technology
1 File
Productivity

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.

1 File
Engineering

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.

WordPressGoogle AnalyticsGoogle Search Console+2 more
Sales

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.

ClaudeClaudeG2 Buyer Intent (G2 MCP Server)ZoomInfo (MCP)+3 more

Ishani D.

Account Manager at G2