hyperbuild-7-design-systemslisted

Step 7 of the hyperbuild pipeline — spawns 3 hb-design-system-author subagents in parallel (one per design direction from step 6). Each author reads its direction's research doc and writes a complete design system: runs/<run_tag>/designs/<a|b|c>/design-system.md + tokens.css — a named signature element, a display+body type pairing, light+dark color palettes, spacing, a shape language, a named depth model, motion, illustration/empty-state art direction, data personality, and component specs (buttons, cards, inputs, nav, lists, empty states). docs/DESIGN-CRAFT.md is BINDING on this step. tokens.css follows the three-layer token structure (primitive → semantic → component) unless the direction's research argues otherwise, and must carry real layered elevation, a radius rhythm, both type faces, and motion tokens. Step 8's mockup smiths inline these tokens verbatim; /hyperbuild-choose copies the winning tokens.css to app/design/ and step 13 implements it in the target framework. Invoked by the hyperbuild router vi
zakariaf/hyperbuild · ★ 0 · Web & Frontend · score 72

Install: claude install-skill zakariaf/hyperbuild

# Step 7 — Design systems (parallel, 3 authors) You are executing step 7 (design-systems) of the hyperbuild pipeline. Step 6 produced one research doc per design direction plus the letter↔direction mapping; step 8 will build HTML mockups of every PRD screen directly from the tokens and component specs you produce here. **Goal:** three complete, independently authored design systems on disk — `runs/<run_tag>/designs/<a|b|c>/design-system.md` + `tokens.css` — one per direction, each meeting the craft bar in `docs/DESIGN-CRAFT.md`. **The craft bar is binding.** `docs/DESIGN-CRAFT.md` §3 lists eight commitments every design system must make; this step's required sections ARE those commitments. The failure this exists to prevent: the first real run's systems documented Motion, Elevation, and Empty states beautifully and shipped token sets that produced flat, dated screens — because the documents described craft the tokens never provided and no check compared the two. A design system that reads well and tokenizes nothing is a FAILED design system here. **⚠ CRITICAL: do NOT author the design systems yourself.** Each system is written by an `hb-design-system-author` subagent (opus, tool-locked to Read + Write) with a fresh context holding exactly one direction's research. If you find yourself about to write `design-system.md` or `tokens.css` directly, STOP and spawn the authors. Three systems written by one saturated orchestrator context converge on each other — the exact failure