ui-design-systemlisted

# UI Design System This skill does not have a look of its own. Its job is to take **the user's** design decisions — their palette, type scale, radius tiers, spacing rhythm — and (1) freeze them into one portable `design-tokens.json` the user owns, then (2) hold every UI they generate to that file. A generic UI helper has no memory: it picks a slightly different blue and a slightly different radius each session, and the product ends up looking assembled by five people. The durable value here is **the user's own consistency**, enforced deterministically. ## Division of labor — what is a taste call vs a machine check - **Taste calls** (which blue, serif vs sans, playful vs austere) belong to the user, reached through conversation — draw on `ui-ux-pro-max` for options if they want to explore. This skill never overrides those with a preferred style. - **Machine checks** (is text readable on canvas, is the radius scale monotonic, does this component use a color that isn't in the system) are objective. Those are what the bundled scripts enforce — no opinion, just the user's own tokens applied consistently. ## Workflow 1. **Establish the tokens.** If the user has existing code, harvest what it already uses — `python scripts/design_tokens.py --extract src/` scans the codebase, clusters near-duplicate colors, and prints a tokens *draft* to rename and prune (the system already exists implicitly; you are writing it down). If starting fresh, converse to pin do