design-method

Topics in the source

• Design Method — The Core
• Setup
• Register
• Design Read + the 3 dials
• What each number means — anchored on the corpus
• The screen-holding floor — checked at Gate 0, not after the build
• Setting a dial is a decision, not a field
• Gate 0 — Brief Lock

The core design method and entry point for any design task: resolves the Register (brand vs product), states the Design Read one-liner and sets the 3 numeric dials (DESIGNVARIANCE, VISUALDENSITY, MOTIONINTENSITY) against a scale anchored on the fifteen reference pages, enforces the Gate 0 brief lock before any HTML/CSS/tokens are touched, applies the Absolute bans, runs the 2-level AI-slop test, and routes to the matching move (generate, critique, audit, bolder, quieter, distill, harden, polish, redesign) and its target skill. Read this first — before design-system, any register/.md file, or any moves/.md file. This skill owns the gate and the routing table, not the move procedures themselves. 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. How this core gets loaded, every time, no exceptions: 1. Read this file once per task — not once per move. Skip the re-read for a later move in the same task if

This is an excerpt. Refer to the complete source and its current requirements.