Stop describing your design system in prompts.

What is in the folder

Six things, and one of them does the real work.

Tokens tell the model what blue is. The contract tells it what a button is allowed to be. That second one is what stops the drift.

1. 01637 design tokensW3C DTCG shape across eight foundations, portable rather than tied to one tool.
2. 02Six component contractsYAML, one definition per component, so the model has something to compare against.
3. 03A validatorFails any screen that uses a value outside the tokens. Prompts drift. A test does not.
4. 04RTL rules and an Arabic type layerHeld inside the system, not bolted on as a separate stylesheet.
5. 05A Figma sync scriptPushes the tokens in as variable collections, so the file and the code stop disagreeing.
6. 0619 PDF guidesOne per foundation, written to be read by a person, not generated filler.

Why a contract beats a prompt

An agent drifts from instructions. It does not drift from a failing test.

Writing the contracts is the part that forces the decisions a team has been avoiding. You cannot write down the five things a button may be without admitting the other eleven were mistakes.