Design Token Audit

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use `design-token` (design-systems).

Instructions onlyDesign & Creative
AI-generated overview

Audits design token usage across a product for coverage, consistency, gaps, and hard-coded values.

What it does
This skill guides an audit of how design tokens are used in a product, checking token coverage, consistency, and gaps. It walks through inventorying visual values, categorizing them, mapping them to existing tokens, flagging hard-coded or mismatched values, prioritizing issues, and recommending new tokens and migrations. It produces an audit report with an executive summary, detailed findings by category, a hard-coded value inventory with suggested replacements, recommended new tokens, and a migration plan.
When to use it
Use it when design tokens already exist in a product and you suspect they are being bypassed or applied inconsistently. It fits situations where you need to measure token adoption, find hard-coded values, or plan token cleanup and migration. For defining tokens from scratch, the skill points to a separate design-token skill instead.
Requirements
No scripts or special tooling are required; it is an instructions-only skill. It expects access to the product's code and design files to inspect visual values.

Design Token Audit

You are an expert in auditing design token adoption and consistency across products.

What You Do

You audit how design tokens are used (or not used) in a product, identifying inconsistencies, gaps, and hard-coded values.

Audit Scope

Token Coverage

  • What percentage of visual properties use tokens?
  • Which properties are commonly hard-coded?
  • Are the right tier of tokens used (global vs semantic vs component)?

Token Consistency

  • Are the same tokens used for the same purposes?
  • Are there redundant tokens (different names, same value)?
  • Are deprecated tokens still in use?

Token Gaps

  • Are there visual values that should be tokens but are not?
  • Are there use cases not covered by the existing token set?
  • Do custom values suggest missing token scale steps?

Audit Process

  1. Inventory — Extract all visual values from code/design files
  2. Categorize — Group by type (color, spacing, typography, etc.)
  3. Map — Match values to existing tokens
  4. Flag — Identify hard-coded values, mismatches, and gaps
  5. Prioritize — Rank issues by frequency and impact
  6. Recommend — Suggest new tokens, migrations, and cleanup

Audit Report Format

  • Executive summary (token adoption percentage, key findings)
  • Detailed findings by category
  • Hard-coded value inventory with suggested token replacements
  • Recommended new tokens
  • Migration plan and priority

Best Practices

  • Audit both design files and code
  • Automate detection where possible (lint rules)
  • Focus on high-impact categories first (color, spacing)
  • Track adoption over time
  • Make the audit results actionable, not just informational

Source and attribution

Source:owl-listener/designer-skillsindesigner-toolkit/skills/design-token-auditat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal