design

# Design Systematic, anti-slop product design. All agents inherit the session model. Reviewers bold-labeled; Workers plain. This skill exercises **Layer 4 (Brainstorming/Spec)** and the design layer of **Layer 0 (Project Analysis)**. It is **thinking, not building** — no source code is written here. The only writes are to `.hyperflow/design/system.md` and `.hyperflow/specs/`. It ends with a handoff gate into `/hyperflow:plan` → `/hyperflow:dispatch` for the build. ## Iron Rules - **Design system first.** Every run establishes or extends `.hyperflow/design/system.md` before designing a screen, per [`../hyperflow/design-system.md`](../hyperflow/design-system.md). The system is created once and extended, never regenerated. - **Researched, not invented.** Ground every direction in **≥2** real products from the project's field, combine them, then diverge with one deliberate signature (the method in [`design-system.md`](../hyperflow/design-system.md)). - **Local taste skills are invoked live.** The main session calls `Skill` to invoke the matching taste skill; the dispatched `designer` agent Reads the `SKILL.md` and applies it (it has no `Skill` tool). - **Per-step agents (DOCTRINE rule 12).** No inline design — the [`designer`](../../agents/designer.md) specialist does the work; an `accessibility-reviewer` pass gates the result. - **No code in the design phase.** Design produces a system file and a design spec; `dispatch` executes them. - **Failure recovery (DOCTRINE...