design-systemlisted

# design-system A design system you install into a repo, not a component library you import. It makes taste structural: the material becomes a contract file an agent reads before every UI touch, rejections become memory, and the verdict becomes a step. The one-line test for anything it produces: **a change that makes the surface prettier and the task harder must fail** — that failure is *costume*, and it fails no matter how it photographs. Load [references/doctrine.md](references/doctrine.md) once to calibrate on *why*; it is not needed per-run. ## Gate | Situation | Move | |---|---| | Repo has no `DESIGN.md` / `TASTE.md` | **Install** the system (below). | | System installed, a surface to build or restyle | **Build** → route to kiln with the material loaded. | | A change, diff, or redesign to judge | **Judge** → route to taste. | | A motion decision | route to animate-it. | | Choosing a font, icon set, or decomposing a reference | [references/catalog.md](references/catalog.md), then build. | | One-off with no product life (a throwaway page) | Skip the system. Just build it. | Ceremony scales with stakes. A component tweak in an installed system is a one-line material lookup; standing up a system on a new product is the full install. This skill orchestrates three others that must be installed alongside it: **kiln** (generate + audit surfaces), **taste** (verdict protocol), and **animate-it** (motion). Where they are not present, do the step by hand against this repo's r