Skip to main content

Does your CLAUDE.md ask, or enforce?

A rule in an instructions file can only ask. If the rule has to hold every time, it belongs in something that can refuse: a permission rule, a hook, a required check, or the OS. Paste your file to see which of its lines are written as requests but need to be enforced.

Verdict

2 of 5 lines ask for something that should be enforced.

Move 1 to a permission rule and 1 to a hook.

Checking CLAUDE.md.

Line by line

  1. Line 1 Asks Doesn’t change a decision

    Maintain high quality code.

    Rewrite it as “When $trigger, do $action, then verify $result”, or delete it.

  2. Line 2 Enforce: Permission rule, rung 5 Must hold every time

    Never read .env files.

    Move it to a permission rule: deny Read(**/.env*), and ideally keep the credentials out of the agent’s reach. Likely rung: permission rule.

  3. Line 3 Asks Good operational fact

    Run `pnpm test:billing` from `apps/api` after billing changes.

    Keep it.

  4. Line 4 Enforce: Hook, rung 6 Deterministic

    Format files with Prettier after every edit.

    Hand it to the formatter or a hook, such as PostToolUse. Prose only asks.

  5. Line 5 Asks Stale-prone

    Current branch is feature/invoices-2.

    Move it to the task prompt, or have a SessionStart bootstrapper look it up each time.

Check your own file

Or drop the file here

How this is checked

Each line and bullet is read with a handful of simple word rules. Headings, code blocks, and comments are skipped. Absolute language such as “never” or “do not” next to something tool-shaped, like a file, a command, a branch, or a credential, is a rule that has to hold every time, so it belongs on a rung that can refuse: a permission rule for files and commands, a required check for branches, and the credentials boundary for production. Formatting or linting on every edit belongs in a hook. Everything else can stay a request, though the note under each line says when it would be better as a skill, in the task prompt, or deleted.

These are heuristics, not a description of how any tool behaves, and they only read English. The ladder above is the useful part: ask of every rule which rung it needs. If it matters, make it executable.