design-tokens-sync

Audits and reconciles design tokens between canonical sources and consuming code.

1|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/th-efool/SKILLS --skill design-tokens-sync-th-efool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-tokens-sync
Source: https://github.com/th-efool/SKILLS/tree/main/design-tokens-sync
Command: npx skills add https://github.com/th-efool/SKILLS --skill design-tokens-sync-th-efool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design systems drift over time: hex values get hardcoded in components, tokens get renamed in Figma but not in Tailwind, and stale copies of the palette spread across CSS files. This Skill detects that drift and reconciles everything back to a single source of truth. ## Core Features & Use Cases - Drift Detection: Locates every token definition (tokens.json, Figma variables export, tailwind.config, CSS custom properties, TS theme objects, SCSS variables) and builds a graph of canonical values, downstream definitions, and consumption sites. - Four-Bucket Report: Generates token-drift-report.md classifying issues as stale copies, hardcoded values, orphan tokens, and untokenized raw values, plus a token coverage percentage. - Controlled Reconciliation: Regenerates downstream files from the canonical source, replaces hardcoded values with token references (near-matches only with per-case confirmation), and never auto-deletes orphans. - Use Case: A team discovers their Tailwind config and Figma variables no longer match after a rebrand. Run the audit to get a full drift report, approve the sync direction, and add a CI guard so the drift never returns. ## Quick Start Ask the assistant to audit your design tokens and produce a drift report comparing tokens.json against your Tailwind config and CSS files.

Frequently Asked Questions about design-tokens-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync design tokens between Figma and Tailwind?▼

Export Figma variables, designate one file as the canonical source, then run a drift audit comparing it against tailwind.config theme values. Stale copies are regenerated from the canonical source after you confirm the sync direction.

How to find hardcoded color values in a codebase?▼

Scan components for raw hex, px, rem, and timing values, then match each against existing tokens. Exact matches can be replaced automatically, while near-matches within perceptual color distance require per-case confirmation since they may be intentional.

What token formats does the audit support?▼

The audit reads W3C-format tokens.json files, Figma variables exports, Tailwind config themes, CSS custom properties, TypeScript theme objects, and SCSS variable files. If multiple sources claim to be canonical, you choose which one wins before any changes.

Can I prevent design token drift in CI?▼

Yes, the Skill can add a tokens:check npm script that re-runs drift detection and fails CI on new stale copies or hardcoded near-matches. This keeps the system synced after the initial reconciliation.

Will token renames break my existing components?▼

Renames propagate everywhere or nowhere, since a half-renamed token is worse than keeping the old name. The Skill also preserves semantic layering, fixing references at the correct alias layer instead of flattening to primitives.