Stop Babysitting Your AI — How I Made Claude Code Enforce Its Own Rules

Japanese version: Zenn (Japanese) This is the third in a series. The first two: Solving Claude Code's Memory Loss and 7 Phrases That Make Claude Code Actually Reliable. You don't need to read them, but they give context. Here's something I learned the hard way: writing rules for an AI coding assistant is easy. Getting it to actually follow them is a different sport entirely. I run 25 repos through Claude Code. I have a shared conventions file, session logs, templates, the whole setup. It works. But within two weeks of scaling it up, I found myself repeatedly fixing the same three problems: Claude writing information in the wrong place Convention files bloating until they defeated their own purpose Documentation silently drifting out of sync with reality My first instinct was to add more rules. "Don't write project state to memory." "Keep SESSION.md under 80 lines." "Check references before pushing." Rules on top of rules. It didn't work. Rules get autocompacted. Rules get ignored. Rule