Add or change a design system asset
The system is recipe-first. To change an asset, change its recipe — never patch the output.
Principles
- Every visual asset is generated from a single source of truth.
- Change a constant in the recipe — every surface updates on the next build.
- Append a one-liner to What's new describing the visible result.
Why recipes, not static files
Every visual asset is derived from a recipe so changes propagate everywhere on the next build. If something looks wrong, the recipe is wrong — fix that instead of patching the output.
Changelog rule
Every meaningful visual change ships with a one-line What's-new entry describing what changed and where it's visible.