hyperbuild-redesignlisted

Generate a NEW set of design directions for a run parked at the Stage-A design gate. Invoked directly by the user as /hyperbuild-redesign [notes], where notes are free-form ("bolder, more playful", "keep c, replace a and b", "nothing beige", "more like Duolingo's energy"). Parses KEEP/REPLACE instructions — kept directions survive untouched with their letters, only the replaced slots regenerate — archives everything it replaces under runs/<run_tag>/designs/archive/round-<N>/, then re-runs step 6 (design research) for the new slots with the user's notes appended to the direction brief as binding constraints, followed by step 7 (design systems), step 8 (mockups + screenshots) and the step-8.5 visual QA for those slots only, rebuilds directions.md + designs/index.html, re-runs the step-12 gate and parks the run again. Repeatable — round 2, 3, … each archive their predecessors. Records every round in runs/<run_tag>/decisions/revisions.md. Does NO build work and never touches app/.
zakariaf/hyperbuild · ★ 0 · Web & Frontend · score 72

Install: claude install-skill zakariaf/hyperbuild

# /hyperbuild-redesign — new design directions, nothing lost You are executing a design round on a hyperbuild run parked at the design gate. The user has seen three directions and wants different ones — all three, or only the slots they name. Your job: preserve what they keep, archive what they replace, regenerate the replaced slots under their notes as binding constraints, and park the run at the gate again with a fresh comparison gallery. **THIS SKILL DOES NO BUILD WORK AND NEVER TOUCHES `app/`.** It also does no design work by hand: naming the new directions is yours (step 6.1 is orchestrator work), everything else runs through the owning step skill with its own spawn templates. If you find yourself writing `design-system.md`, `tokens.css`, or mockup HTML from this seat, STOP. **Every design spawn this skill drives reads `docs/DESIGN-CRAFT.md` FIRST.** It is the binding craft bar: §2's twelve anti-patterns are DEFECTS, §3's eight commitments are mandatory sections, §4's layout rules are mechanical facts checked at 8.5. A round that produces three more competent, dated, flat directions has failed even if the user's notes were vague. ## When NOT to use this skill - **After `/hyperbuild-choose` released Stage B.** With `stage: "BUILD"` (or `"DONE"`) the app is being built against a chosen design; design changes then go through step 15's structural-findings path (`hyperbuild-15-adversarial-review`) — its `hb-ux-critic` findings become patches, and structural ones be