Where the theme lives
shadcn/ui's theming documentation uses and recommends CSS variables, set through tailwind.cssVariables in components.json, with the tokens in your CSS file under :root and .dark. Those variables say which values exist. DESIGN.md says how your brand puts them together: which colour signals, which face carries headings, how a card or a hero is built.
Set it up
- Run
npx briefatto-board install. - With the app running, run
npx briefatto-board adopt . --page <url>for each representative route. - The agent reads the captures and computed styles, inspects your CSS variables and theme files, and writes DESIGN.md by role.
- Run
npx briefatto-board freeze .. Freeze records the exact rendered styles, and the block tells every session to read the guide first.
Catch the strays
On a frozen board, board check notes every colour and font a piece paints that is not in the current guide. Add --consistency for a kit format to list each off-palette colour with its nearest frozen colour.
Questions and answers
Does DESIGN.md replace components.json or my CSS variables?
No. shadcn/ui keeps the theme; DESIGN.md is the brief the agent reads before it uses it.
Can DESIGN.md refer to my variables by name?
Yes. Describe them by role in the prose. Freeze compares the colour values written in the guide with the render, and reads a braced reference as a token name.
Is Briefatto Board free?
Yes. It is open source under the Apache-2.0 licence and installs with npx briefatto-board install.