token-build

Solid

Set up or run the token build pipeline — transform the DTCG tokens/*.json (source of truth) into platform artifacts (CSS variables, Tailwind @theme, JS/TS, iOS Asset Catalog, Android, Compose) with Style Dictionary / Tokens Studio / W3C DTCG export. Use when the user wants to generate platform theme files from tokens, wire token CI, or multi-platform token output.

Web & Frontend 731 stars 77 forks Updated today

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

Description 5%

100

Skill Content

# Skill: Token Build Turn the DTCG token source of truth into platform-ready outputs. Tokens are authored once; every platform output is generated. ## Steps 1. Read `workflows/token-build.md` (architecture, tool options, resolution rules, output targets, CI). 2. Pick the tool: **Style Dictionary** (multi-platform, the default), **Tokens Studio** (Figma-owned tokens — pairs with `figma-integration`), W3C DTCG export, or a small custom script (model on `scripts/validate_tokens.py`). 3. Honor the resolution rules: resolve aliases to final values per platform; expose semantic + component tokens (primitives stay internal); emit base + dark/brand/density overrides (`tokens/theming.json`) as deltas only; format by `$type`. 4. Generate the requested target(s): CSS `:root` vars, Tailwind v4 `@theme`, typed JS/TS, iOS Asset Catalog + `Color.DS`/`Spacing`, Android `colors.xml`/Compose theme. 5. Wire CI: on `tokens/*.json` change, run `scripts/validate_tokens.py`, regenerate, fail if committed artifacts are stale; gate colors with `scripts/contrast.py`. ## Verification (definition of done) - `python3 scripts/validate_tokens.py` passes (no unresolved aliases). - Regenerating produces no diff vs. committed artifacts. - Dark/brand/density outputs contain only deltas, not full duplicates.

Details

Author: plugin87
Repository: plugin87/ux-ui-agent-skills
Created: 5 months ago
Last Updated: today
Language: JavaScript
License: None

Integrates with

Tailwind CSS · Frontend

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

design-tokens

Generate, extend, or audit design tokens in DTCG format with the 3-tier architecture (primitive → semantic → component). Use when the user wants a color palette, type scale, spacing/shadow/radius/motion tokens, multi-brand theming, or wants to validate token files. Covers colors, typography, spacing, shadows, borders, breakpoints, motion, gradients, opacity, blur, sizing, states, theming.

731 Updated today

plugin87

Web & Frontend Listed

design-token-builder

Expert design token engine that interviews the user and generates a structured, semantic tier-3 Design Token JSON file (W3C DTCG format) plus a mandatory HTML preview, adhering to platform and accessibility standards. Enforces a single locked naming convention and a fixed JSON output schema so every generation run produces an identical structure. Use this skill whenever the user wants to build, generate, audit, or update a design token system — color/typography/spacing/radius/border/elevation scales, a multi-brand or multi-theme (Light/Dark) token set, or wants those tokens wired directly into a Figma file as Variables and Foundation documentation pages — even if they only say 'set up our design tokens' or 'build a Figma variable library' without using the words 'design token' explicitly.

0 Updated 3 days ago

Blingkusano

Web & Frontend Listed

design-tokens-pipeline

The single source of truth for design values — author tokens in W3C DTCG format, build them through Style Dictionary into CSS custom properties, and consume them 1:1 in Tailwind v4's @theme. Use when setting up a token system, naming or aliasing tokens, wiring a Figma/Penpot export into code, or deciding where a color/spacing/type value should live. Triggers on "design tokens", "DTCG", "Style Dictionary", "@theme", "token pipeline", "where does this color come from".

0 Updated 1 months ago

BenMacDeezy