AI Blocks › Design things people love
Monthly design consistency review
Give it your product's code each month. Get the drift from your design rules found, contrast checked and a spec to approve.
Monthly design consistency review is a free AI agent for the job "Design things people love". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks · Level: advanced · Thinking: high
What it does
A design system is written once and then the code moves on. A new screen hardcodes a green that is almost the token. A button grows a fourth variant nobody documented. A spacing value appears that is close enough. Each is small. After a year the product has three shades of the brand colour and nobody can say which is right. This agent reads the code every month. It writes the rules from what the product really uses and you approve them. Then it counts the drift, hardcoded values, naming problems and undocumented variants, with the file and line for each, and says when the count has risen two months running. It checks every colour pair when a token moves, catches spacing and type slips on the screens that changed, and once a quarter reviews the whole against ten principles, proposing removals before additions. Any new pattern that passes review…
You give it
- Your repo or front-end folder with components and styles
- Your design file, so intent can be compared with code (advised)
- Your brand guide with colours, type and rules (advised)
- The screens or releases that changed this month (advised)
- Last month's keeper file, once it exists
- Brand brain (optional)
- Brand guide (optional)
- A buyer brief (optional)
You get
- A DESIGN.md of the colours, type, spacing and parts the product really uses, for you to approve
- Every drift item with file, line and the token or name it should use, counted against last month
- Failing colour pairs with the closest passing colours
- Spacing, type and layout slips on changed screens, each with a fix
- A quarterly ten-principles review with what to remove
- A spec for each new pattern, and a fix list of at most fifteen
Use it when
- You have a design system and suspect the code has drifted from it.
- A brand refresh changed a colour and you are not sure every pair still passes.
- New screens ship every month and nobody checks them against the rules until a designer notices.
How to use it
- Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then point it at the repo.
- On the first run, read and approve the design rules it writes from the code. They are saved.
- Each month, tell it which screens or releases changed. Attach the design file if you have one.
- Read the drift and the fix list. Make the changes you agree with, then tell the agent which were done.
- Run it again on the first Wednesday of next month. It tracks the drift count over time.