CodingClaude CodeClaude
Write the design canon once, then point every agent at it
A single DESIGN.md with tokens and rules beats re-explaining the look in every prompt.
Agents are great at following rules and terrible at guessing taste. So write the taste down.
My apps share one DESIGN.md: palette tokens, bevel recipe, font rules, and a short list of things I have rejected before with the date and the reason. Every UI task links to it. The reason line is the important part: "no caption buttons — 2026-08-27, they were decorative" stops the same mistake from coming back next month.
- Tokens first, components second, rules last.
- Record rejections with dates. Agents read the history.
- Keep it under two screens. If it grows, split it.
The payoff is that a new agent session produces something on-brand on the first try, and reviews become "does it follow the canon" instead of "do I like it".