Prompt
Build <component> in this codebase.
Colour, spacing, radius and type come from the token file at <path>. Read
it before writing anything. No hex, rgb, oklch or bracketed arbitrary values
outside that file.
Text on a coloured surface uses that surface's paired ink token. Dark mode
uses the same tokens, not overrides.
If the design needs a value the tokens do not have, stop and list each one
as: what the design shows, the nearest token, the difference. Do not invent
a token and do not write the literal.
End with the tokens you used and any values you could not map.When to use it
Any time an agent builds or edits a component in a codebase that has a token file and the tokens-first skill is not installed. Fill in the component and the path.
Why the shape works
"Match the design" is a target the model can only approximate, so every run lands slightly differently. Naming the token file turns the task into picking from an enumerable set. The stop-and-list clause is the guardrail: a value with no token becomes a question for you instead of a hex in the code. The full argument is in Design tokens as machine-readable guardrails.