There's an exceptional idea buried in this which flies under the radar in my experience: If we're writing a document that polices the model behavior, we're alt

There's an exceptional idea buried in this which flies under the radar in my experience: If we're writing a document that polices the model behavior, we're altering every version of the model+harness we use henceforth. Most things I wrote in a Claude.md because Opus 4.something was crap had roots in Opus, Claude Code, system prompts, and our own bad code we wrote last year. None of these things exist today but the Claude.md file can stick around like it's all still necessary. I too am morally opposed--I abide by a 100 line (short lines, not paragraphs) limit and edit it rarely. Most of my annoyances have come and gone, meanwhile I've gotten better at producing 4 good sentences of prompt for most things instead of 4 bad sentences. And we actually have CLI tools that can communicate effectively so instead of telling the model what "gates" to care about, we let the tooling surface area and output express what's important.