What each holds
Tailwind config or @theme | DESIGN.md with Briefatto Board | |
|---|---|---|
| Holds | Theme variables that decide which utility classes exist | Layout, components, type and voice by role, plus exact styles recorded from a render |
| Read by | Tailwind, when it compiles your CSS | The agent, before any visual work |
| Answers | Which values are available | How the brand uses them, and what a new piece should look like |
| Versioned | With your code | Frozen as v1, v2 and on, with a stale list after a change |
How they stay in step
Tailwind's documentation says theme variables defined with @theme become regular CSS variables when your CSS is compiled. After board adopt, the agent inspects those CSS variables and your Tailwind configuration, and board freeze records the computed styles your pages actually render. Freeze then names any style value in the prose that conflicts with them.
Questions and answers
Should DESIGN.md replace tailwind.config?
No. Keep your theme where Tailwind reads it. DESIGN.md is the brief the agent reads before it uses that theme.
Does it work with Tailwind's @theme variables?
Yes. The agent reads the CSS variables they compile to, and freeze records the styles they produce on your pages.
Is Briefatto Board free?
Yes. It is open source under the Apache-2.0 licence and installs with npx briefatto-board install.