design-method

<!-- Grounding: grounding-corpus.md §A (impeccable anatomy — thin router, Register, dials, Absolute bans, 2-level slop test), §G (root-cause fix: template reproduction demoted, register-first), §H (kept anchors: Gate 0, Signature Dominance, Focal-Block Floor, Competitor Lift Test, MOTION_INTENSITY). --> # Design Method — The Core This is the one place the design pipeline is defined. The agent (`agents/design-expert.md`) always loads this file before dispatching to a move; every `references/register/*.md` and `references/moves/*.md` file assumes you've read this first and references it instead of restating it — if a rule elsewhere contradicts this file, this file wins. ## Setup How this core gets loaded, every time, no exceptions: 1. Read this file once per task — not once per move, once per task. If a second move runs later in the same task and nothing about the Register or the codebase changed, don't re-read it. 2. **Read `../design-system/SKILL.md`** — always, unconditionally, before anything else below. It's a thin, pointer-only file, cheap to reload; this exact read is also the harness's phase-1 trigger, so it happens even on a task that turns out to need no new token. Existing `design-system.md` tokens still win over its defaults once resolved. 3. Resolve **Register** (below), then write the **Design Read + 3 dials** one-liner. 4. Pass **Gate 0 — Brief Lock** (below) before touching any HTML/CSS/tokens. 5. Read the ONE matched `references/moves/<move>...