---
title: "Comment by Ahmet Özel on \"A Working CLAUDE.md/AGENTS.md Template You Can Copy Today\" | Hashnode"
description: "\"Vague prose doesn't change agent behavior any more than it changes a new hire's behavior on day one\" is exactly right, and the comparison holds further than it"
url: "https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0cbfd8f1a195078ac4fc4"
---

[Discussion](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906)

Comment [A Working CLAUDE.md/AGENTS.md Template You Can Copy Today](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906)

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Sep 21](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0cbfd8f1a195078ac4fc4)

"Vague prose doesn't change agent behavior any more than it changes a new hire's behavior on day one" is exactly right, and the comparison holds further than it first looks. What actually changes a new hire is a failing test, a linter and a review that blocks, not the onboarding doc. Same here: the rules that survive are the ones something else enforces.

The pattern that has worked best for me is treating the file as a pointer to enforcement rather than a substitute for it. State the rule, then state which check fails when it is broken.

Anything in the file with no corresponding check is a preference, and marking it as one keeps the genuinely load-bearing lines from being diluted.

[Dhrutika Rathod](https://hashnode.com/@dhrutikarathod)

[Sep 21](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0cbfd8f1a195078ac4fc4#reply-6ab0cda0baca9a76315aaf5c)

the pointer-to-enforcement framing is a great way to think about it. Appreciate you sharing this, definitely something worth building on.

[Ahmet Özel](https://hashnode.com/@ahmetozel)

[Oct 4](https://hashnode.com/posts/a-working-claude-md-agents-md-template-you-can-copy-today/6ab0b5315dae22d9c2402906/comment/6ab0cbfd8f1a195078ac4fc4#reply-6ac296a78e7de5c668c30bbb)

A useful extension would be to give each enforced rule its exact check name and a short example of the failure it catches. Then someone reviewing an agent change can run the relevant check without translating the prose into a guess about which test applies.

I would also qualify my earlier statement: a rule without an automated check can still be a real constraint. Marking it as requiring human review is more accurate than treating every unenforced rule as an optional preference.
