What the guide moves
A lot. In our drift test, agents with no design file matched the brand's fonts in 0 of 18 pieces, and their palettes wandered from session to session. With a DESIGN.md they matched the fonts in 53 of 54 pieces and brand colour coverage reached 99%.
That is the brand arriving. It says nothing about whether a headline fits its box at the size the post is seen.
What only the check catches
- Plumb. The signal colour changed in v2 and the link card was redrawn from the new guide.
board checkfailed it: a 16px label where 22px was the minimum where it is seen. Raised to 26px, it passed. - Afterlight Matinees. During the direction round, the check caught an off-canvas offer, start time, door time and call to action, and a date line running past the mobile canvas. The agent fixed all of it before the client approved.
Both pieces were made with the brand in hand, and both failed the floor until they were fixed.
Wire both in
After board freeze, the block in AGENTS.md and CLAUDE.md tells the agent to read DESIGN.md before any visual work and to run board check on every piece before handing it over. The check sets exit status 1 when a piece fails, so the same command can gate a commit:
npx briefatto-board check .Git aborts the commit when a pre-commit hook exits non-zero. Set up the hook.
Questions and answers
Isn't a review step just another prompt?
No. board check is a program run on the rendered page, so it costs no model tokens and gives the same answer every time it runs.
Does the check judge taste?
Taste stays with the model, which makes every aesthetic call. The check fails what can be measured: clipped, off-canvas, overlapping or too-small text, fonts that never loaded and contrast below WCAG, plus the Impeccable detector's pattern rules.
What does the check write down?
A receipt, check.json: every check that ran, every one that was skipped and why. A pass with a skipped contrast check says so.