alt Hacker NewsThey shouldn’t make it into the product/build, but if you think about them as documentation, it makes sense to version control them.
They often describe:
- Overall architecture
- Repository layout
- Processes to use
- Things not to do: code styles to avoid, libraries to not use, etc.
While they’re primarily documenting these things for an agent, the information is similarly useful to a human.
Replies
morkalork • today at 2:54 PM
Yeah, having one that's consistent across team members is 100% better than everyone having their own each with their own quirks
That's like 10% of the reason why people would commit CLAUDE.md…
The number one reason is, you are on a 10-dev tea and it just doesn't make sense for everyone to waste their token budget creating separate instances of this file, which an also requires ingesting the othe whole repo... That is 50, 60%.
The other bit is that you have a review pipeline hooked into CI/CD, and it is the easiest way to tell the bot how to review your code.