Skip to content
cccskills
FreePublished on GitHub

design-tokens-sync

Audit and sync design tokens between the source of truth (tokens.json, Figma variables export) and the code that should consume them (Tailwind config, CSS custom properties, theme files). Finds drift -- hardcoded values, orphan tokens, out-of-date copies -- and fixes it in the right direction.

The English summary is being prepared. Showing the original description.

Works withFigma

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Design Tokens Sync

Keep one source of truth actually true. Every design system decays the same way: a hex gets hardcoded in a hurry, a token gets renamed in Figma but not in Tailwind, a second half-copy of the palette appears in a one-off CSS file. This skill finds the drift, decides direction with the user, and reconciles.

Workflow

  1. Locate the truths. Find every place tokens are defined: tokens.json/*.tokens.json (W3C format), Figma variables export, tailwind.config.* theme, CSS custom properties, TS theme objects, SCSS variable files. If more than one claims to be canonical, ask which wins before touching anything -- direction of sync is a human decision.
  2. Build the graph. For each token: canonical value, every downstream definition, and every consumption site. For each raw value in code (hex, px, rem, ms, cubic-bezier): whether a token exists for it.
  3. Drift report. Output token-drift-report.md in four buckets:
    • STALE COPIES -- downstream definitions that no longer match canonical (with both values)
    • HARDCODED -- raw values in components where a matching token exists (exact match, then near-match within perceptual distance for colors)
    • ORPHANS -- tokens defined but consumed nowhere
    • UNTOKENIZED -- raw values appearing 3+ times with no token; these are tokens waiting to be named
  4. Reconcile on approval. Stale copies: regenerate downstream from canonical. Hardcoded: replace with token references -- exact matches automatically, near-matches only with per-case confirmation (that slightly-off blue might be intentional). Untokenized: propose names following the existing convention and add to canonical. Orphans: list for deletion; never auto-delete.
  5. Guard. Offer to add the cheap tripwire: a script (npm run tokens:check) that re-runs the drift detection and fails CI on new stale copies or hardcoded near-matches, so the system stays synced after you leave.

Rules

  • Never sync both directions in one run. Canonical wins; anything flowing the other way (a designer wants the code's newer value) is an explicit canonical edit first.
  • Near-match replacement is per-case, never bulk. #0B1121 vs #0b1220 may be drift or may be a decision.
  • Preserve semantic layering: if the system has color.blue.500 -> color.accent -> button.bg, fix references at the right layer instead of flattening everything to primitives.
  • Renames propagate everywhere or nowhere -- a half-renamed token is worse than the old name.
  • Respect generated files: if theme.css is built from tokens.json, fix the source and rebuild; never hand-edit output.
  • The report quantifies health: token coverage percentage (tokenized vs. raw values in components) is the number to move release over release.

Quick Commands

  • "Audit my tokens" -- steps 1-3, report only
  • "Sync from [source]" -- full reconciliation with the named canonical
  • "What's hardcoded?" -- the HARDCODED bucket only
  • "Add the CI guard" -- step 5 standalone

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

Use to test whether an AI agent, prompt, or skill actually works before or after it ships — build a small eval set, score runs, and catch regressions when the prompt or model changes. Trigger when the user asks whether a prompt is good, wants to compare models or versions, sees inconsistent agent output, or is about to put an agent in front of customers.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills368Updated Oct 20, 2026

See all skills by OneWave-AI

Report a problem with this skill