Ask HN: Do you still spend time maintaining Claude.md / AGENTS.md files?
11–17 of 17 posts
Re: Ask HN: Do you still spend time maintaining Claude.md / AGENTS.md files?
#12Put your coding guidelines in the ./claude/rules for additional progressive disclosure, not CLAUDE.md or AGENTS.md.
Re: Ask HN: Do you still spend time maintaining Claude.md / AGENTS.md files?
#13Re: Ask HN: Do you still spend time maintaining Claude.md / AGENTS.md files?
#14Facts (directory organization, commands, references in docs), always work. There’s no discussion here.
Constraints related to regression prevention (specifying certain restrictions based on a particular failure) – work consistently if each individual item doesn’t exceed one sentence and describes a failure I’ve already observed. Example: “Validate JWT at the route level, not the component.” It works since the agent was caught doing it incorrectly. “Always call workspace provisioning when creating a user” – ditto.
Behavior rules (rules regarding comments, naming, dos and don'ts) – this is where the OP fits in. My observation: such rules work if they are concise, specific, and based on an already existing failure pattern. They don’t work if created in anticipation of some failure that didn’t happen yet. Rules made from scratch are usually not followed. The 50 line limitation is justified for this category.
Re: Ask HN: Do you still spend time maintaining Claude.md / AGENTS.md files?
#15When I start a project, I'll point the agent to a few big behavior concepts on my own standards and preferences, we iterate on the project specific stuff, and once the shape is locked in I point it to the repo to look for relevant patterns.
Once that is covered, it's off to the races. That being said, I don't consider myself an agentic coding power-user.