Writing a Course on Encoding Design System Rules for AgentsWriting a Course on Encoding Design System Rules for Agents
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
The fix for an agent that keeps getting your design system wrong isn't a better prompt.
It's putting the rules where the agent reads them.
In the repo. In skills. In checks it can run itself.
Writing a course about exactly this.
Vara's avatar
This is a game changer for teams managing large design systems. Is this powered by standard code checkers or a custom tool you built?
Anas's avatar
So inspiring 👏! Thank for sharing this valuable insight 👌
Muhammad's avatar
Nice work!
Lauri's avatar
Thanks!
Tran's avatar
What sells it for me is the refusal telling the agent exactly where the token should go. A bare "no hex" error usually just sends it looping. Does guard.mjs run only as an agent hook, or in pre-commit too so it catches humans as well?
Vansita's avatar
Keeping rules in the repo makes sense.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started