designkit

Run the init mode, which scans your stylesheets and components for color literals, font sizes, spacing values, and radii, clusters near-duplicates, and writes a stamped DESIGN.md at the repo root. Every token must be a value that actually appears in your code.

DESIGN.md is an open format from Google Labs (google-labs-code/design.md) pairing YAML design tokens with prose rationale across eight canonical sections. The schema is alpha and read at run time via the official @google/design.md CLI rather than hardcoded.

Yes, the extraction engine checks token homes in order: Tailwind @theme or config, CSS custom properties in :root, SCSS or Less variables, CSS-in-JS theme objects, and WordPress theme.json. If none exist, it clusters hardcoded values and proposes a system from them.

Yes, audit mode is read-only and reports drift in both directions: tokens in the file that no longer appear in code, and values in the code that no token covers. It also diffs against the stamped git SHA baseline when reachable.

The skill degrades loudly: it extracts and writes from a bundled fallback schema, skips lint and export, and explicitly states in its report that validation did not run. It never claims a file is clean when nothing checked it.

No, it deliberately writes no components, pages, or CSS, and never invents values not present in the codebase. Undersivable sections are declared in the spec's omitted field rather than filled with invented tokens.