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.

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?

Really liked how these designs turned out! Explored a concept for AI SaaS product, focusing on a clean interface and a simple, intuitive chat experience. Tried two different layout variation for the hero section. Which would you like?

Really clean concept! 👏

I like the second layout more — the headline "Your ideas deserve an intelligent partner" + the chat preview below makes the AI feel real and easy to use immediately. The first one is also clean, but this one sells the product faster.

I also design SaaS...