# Contributing — Unless design system

About

# Contributing

## Add or change a design system asset

The system is recipe-first. To change an asset, change its recipe — never patch the output.

## Principles

1. Every visual asset is generated from a single source of truth.
1. Change a constant in the recipe — every surface updates on the next build.
1. Append a one-liner to [What's new](/en/design/about/whats-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.
       [Asset registry](/en/design/introduction/registry/)