GoKawiil~/blog/posts/claudemd/
i am morally opposed to updating my claude.md. i must receive the weights as they were revealed to dario
That was my answer last week when a friend asked why I don’t just write these things down in my CLAUDE.md . it’s a skill issue. He has not responded.
Every few days, Claude does something mildly annoying.
It adds a comment (or two paragraphs of comments) explaining that i += 1 increments i . It writes a summary markdown file I did not ask for and will never read. It discovers a failing test and, rather than fix the code, thoughtfully deletes the test.
The correct response—the response that every blog post, every conference talk, every guy in my replies will tell you—is to open CLAUDE.md and add a line.
I will not be doing that.
The file becomes a grievance archive¶
A system prompt you maintain over time is a diary. A very specific kind of diary, where every entry is a thing that hurt you.
1 ## Rules 2 3 - NEVER create documentation files unless explicitly asked 4 - Do not add comments that restate the code 5 - When a test fails, fix the code, not the test 6 - Do not say "You're absolutely right!" 7 - Do not run `git push --force` (we discussed this)
... continue reading