The design QA critic

Build-along · ~10 min at your own keyboard

Same fresh-context principle as code review, pointed at design: a critic agent that checks every outgoing artifact against your brand file and a taste checklist — hierarchy clear? one accent? scannable in 5 seconds? It catches the sloppy fifth-artifact drift you've stopped seeing.

The long version: A design critic ↗

Do this

0/4

Checkpoints

▸You should now see a checklist with brand.md rules and four taste rules.
▸You should now see the critic running with only the checklist and the artifact.
▸You should now see a findings list you sorted into legit and not.

The three ways this goes wrong

The critic gives vague notes ('looks fine'). — Make each checklist item a yes or no question it must answer.
The critic rewrites the design. — Tell it to report findings only. Fixing is your job.
It misses a flaw you can see. — Add a rule for that flaw to the checklist and run it again.

Share what happened

Paste the critic's findings and which you accepted.

Strip API keys, passwords, and tokens before you paste. Swap them for [KEY].

🔒 Don't paste confidential, personal-health, or payment info.