Design System Audit — Health & Coverage Check

Comprehensive audit of a Figma design system's health: token coverage, component structural quality, variable usage, naming consistency, and style completeness. Combines multiple tools into a single audit workflow.

Skill Boundaries

• Use this skill to audit an existing design system's health.
• If the task is building a new design system, switch to figcraft-generate-library.
• If the task is auditing a single component, switch to component-docs.
• If the task is linting a design page, switch to design-lint.
• If the task is comparing tokens against a spec, switch to spec-compare.

Workflow

Step 1: Connect and Load Tools

get_mode                                      → verify connection + get designContext
load_toolset("components-advanced")           → component audit tools

If `get_mode` fails (plugin not connected): STOP. Do not fall back to other MCP servers. Tell user: open Figma → Plugins → FigCraft → wait for connection, then retry.

Note: variables_ep and styles_ep are core tools — always available, no toolset loading needed.

Step 2: Inventory — What Exists

Run a full inventory of the design system file:

get_document_info                             → list all pages
get_current_page(maxDepth: 1)                 → overview per page
components(method: "list")                    → all local components
variables_ep(method: "list")                  → all local variables
variables_ep(method: "list_collections")      → all variable collections
scan_styles                                   → all local styles (paint, text, effect)

Compile an inventory summary:

• Total pages, components, component sets, variables, styles
• Variable collections with mode counts
• Component distribution across pages

Step 3: Component Health Audit

audit_components                              → structural health scan

For each page with components, check:

• ⚠️ Missing descriptions — components without documentation
• ⚠️ Unexposed text — text nodes not editable via properties
• ⚠️ Empty components — no visible children
• ⚠️ Single-variant sets — component sets with only one variant
• ⚠️ Unbound properties — properties not connected to child layers

Step 4: Token Coverage Audit

For each component, inspect variable bindings:

nodes(method: "get", nodeId: "...")           → read component properties

Check:

• ✅ Fill colors bound to variables
• ✅ Stroke colors bound to variables
• ✅ Spacing (padding, gap) bound to variables
• ✅ Corner radius bound to variables
• ✅ Text styles applied
• ✅ Effect styles applied
• ⚠️ Hardcoded values where tokens exist

Calculate token binding rate: (bound properties / total bindable properties) × 100%

Step 5: Variable Quality Audit

Efficient pattern: Use variables_ep(method: "list") — returns ALL fields (name, scopes, codeSyntax, description, valuesByMode) in one call. Do NOT call get on each variable individually.

variables_ep(method: "list", collectionId: "<id>")   → all variables with full details

For each variable, check:

• ⚠️ ALL_SCOPES — variables without specific scopes pollute property pickers
• ⚠️ Missing code syntax — breaks Dev Mode round-tripping (check codeSyntax field)
• ⚠️ Missing description — undocumented variables
• ⚠️ Duplicate raw values in semantic layer — should alias primitives instead
• ⚠️ Orphan variables — variables not bound to any node
• ⚠️ Naming inconsistency — mixed casing or naming conventions

Bulk fix: Use variables_ep(method: "batch_update") to fix multiple issues in one call:

variables_ep(method: "batch_update", updates: [
  { variableId: "...", scopes: ["FONT_FAMILY"], codeSyntax: { WEB: "var(--font-family-brand)" } },
  { variableId: "...", description: "Primary background color" },
  ...up to all variables that need fixing
])

This reduces N individual update/set_code_syntax calls to 1 batch call.

Step 6: Naming Audit

Scan all nodes for naming issues:

lint_fix_all(categories: ["naming"])          → check naming rules

Additionally check:

• ⚠️ Default names ("Frame 1", "Rectangle 2")
• ⚠️ Inconsistent casing (mixed camelCase/kebab-case/PascalCase)
• ⚠️ Duplicate component names
• ⚠️ Missing page separators between sections

Step 7: Generate Audit Report

Compile a structured report:

## Design System Audit Report

### Summary
- Components: X total (Y sets, Z standalone)
- Variables: N across M collections
- Styles: P text, Q paint, R effect
- Token binding rate: XX%
- Health score: X/10

### Component Health
- ✅ With descriptions: X/Y
- ⚠️ Missing descriptions: [list]
- ⚠️ Unexposed text: [list]
- ⚠️ Single-variant sets: [list]

### Token Coverage
- ✅ Bound fills: X%
- ✅ Bound strokes: X%
- ✅ Bound spacing: X%
- ⚠️ Hardcoded values: [list with suggestions]

### Variable Quality
- ⚠️ ALL_SCOPES variables: [list]
- ⚠️ Missing code syntax: [list]
- ⚠️ Orphan variables: [list]

### Naming
- ⚠️ Default names: X nodes
- ⚠️ Placeholder text: X nodes

### Recommendations
1. [Priority fixes]
2. [Quick wins]
3. [Long-term improvements]

Health Score Calculation

Score 8–10: Healthy. Score 5–7: Needs attention. Score < 5: Significant gaps.