Writing rules for my AI agents didn't work. Turning them into checks did.
by•
I build my product with AI coding agents every day, and I keep a file of rules for them. Some rules are in capital letters now because I had to repeat them.
One rule was "never push to main until the tests pass." An agent pushed anyway, and we had to roll it back.
So we turned that rule into a check that blocks the push until the tests pass. Today it even stopped me.
My takeaway: a written rule is a reminder, a check is a guarantee.
Which of your agent rules did you turn into checks, and which are you fine leaving as plain instructions?
30 views

p/runevr
p/producthunt
p/google-cloud-platform
p/aperture-7
p/raycast
p/kuc-kuc
p/lasso-11
p/kodlo
p/ai-context-flow
p/offiai
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/supabase
p/jev
p/htmldrag
p/murror
p/nexupira
p/jot-2-0
Replies
this matches something I run into constantly doing PH outreach through an agent loop - my rule used to be "screenshot after typing into a comment box before submitting, since text can silently fail to land." written down, it got skipped half the time because nothing forced the check. the fix wasn't a stronger reminder, it was making the screenshot a mandatory step the submit action can't happen without. same lesson as yours: a rule an agent can choose to skip isn't a rule, it's a suggestion. the ones I still leave as plain instructions are the judgment calls - tone, how much to push back on something - those don't have a pass/fail condition you could even write a check for
@galdayan "A rule an agent can choose to skip is a suggestion." That's it exactly. And agreed, tone has no pass/fail, so those stay as instructions for me too. Do you keep those in the same file as the hard rules, or separate?
@ashish_khandelwal11 same file, just split into two sections. keeping them together means whenever I touch the rules file I see both lists side by side, which makes it obvious when a "judgment call" rule has actually hardened into something with a clear pass/fail - like Sergey's example below, a money/side-effect rule should graduate into a check. a separate file would make that drift easy to miss
@galdayan Same file, two sections is smart. Seeing them side by side is exactly how you'd spot a rule that's ready to become a check. Stealing that for my own file, thanks Gal!