Design tokens pipeline 1.2.2 stable

Validate JSON token files and build CSS custom properties — including fonts and motion blocks. Token defaults are AAA-oriented (not app certification). Deutsch: Design-Tokens-Leitfaden

Maturity: Tokens CLI and CSS custom properties are stable in 1.2.0. Plan / review / agent meta remain beta / foundation. Studio and the complete Utility Engine stay planned.

When to use

Validate and build design tokens for themes and motion.
Pin @birdapi/velinstyle@1.3.0; keep Studio / Utility Engine out of scope.

When not

Do not treat beta plan/review/meta as a finished AI design system.
Do not invent Studio or Utility Engine APIs that are still planned.

Validate

velinstyle tokens validate --input examples/tokens.sample.json
npm run tokens:validate

Checks OKLCH syntax, theme names, and fonts, motion, zIndex blocks.

Build

velinstyle tokens build --input examples/tokens.full.json -o src/tokens-generated.css

Emits @layer tokens with :root, per-theme overrides, optional displayP3, plus fonts, motion, and zIndex sections (deterministic key order).

Schema

See examples/tokens.schema.json and examples/tokens.full.json in the framework repository.