Review CLAUDE.md for Token Waste
Find vague, repeated, or unused CLAUDE.md instructions that cost tokens every Claude Code turn without improving behavior.
Direct answer
To review a CLAUDE.md for token waste, look for generic rules, repeated advice, long explanations that do not change behavior, stale project notes, and instructions that are already enforced by tooling. Keep commands, repo boundaries, concrete do-not-do rules, and workflow constraints; delete or shorten anything that only sounds helpful.
Open CLAUDE.md ReviewerWhen to use this
- Your CLAUDE.md has grown over many sessions.
- Claude Code responses are slower or more verbose than expected.
- The file contains generic rules such as be careful, write good code, or think step by step.
Steps
- Paste the full CLAUDE.md into the reviewer.
- Mark generic rules that do not change agent behavior.
- Deduplicate repeated style, testing, and safety instructions.
- Keep concrete commands, repo boundaries, and file ownership rules.
- Commit the smaller file and watch whether agent behavior stays stable.
Example review focus
# CLAUDE.md ## Rules - Always write high-quality code. - Be careful and thoughtful. - Use best practices. - Think step by step. - Explain clearly but be concise. ## Project This is a TypeScript app.
Keep the project and commands. Remove generic behavior rules that apply to every repo. Replace them with concrete instructions such as `npm run lint` before final, use `apply_patch` for edits, and do not modify generated files unless the task requires it.
Common mistakes
- Do not delete commands or repo boundaries just because they are long.
- Do not keep motivational rules that cannot be verified.
- Do not optimize only for token count if the remaining file becomes ambiguous.
FAQ
- What counts as token waste in CLAUDE.md?
- Repeated rules, generic advice, stale project history, and long explanations that do not change what the agent should do are usually token waste.
- Should CLAUDE.md be as short as possible?
- No. It should be as short as it can be while still carrying the project-specific commands, boundaries, and behavior rules the agent needs.
- How often should I review it?
- Review it after major workflow changes, new deploy targets, new test commands, or any period where agents keep making the same mistake.
Related CLAUDE.md guides
CLAUDE.md Missing Commands Checklist
Check whether a CLAUDE.md includes the build, test, lint, dev server, deploy, and verification commands an agent needs before editing.
CLAUDE.md Repo Boundaries and Rules
Write CLAUDE.md rules that tell agents which files to edit, which files to avoid, and how to handle dirty worktrees safely.
Review CLAUDE.md Before Converting to AGENTS.md
Clean a CLAUDE.md first, then convert it into AGENTS.md, Cursor rules, GitHub Copilot instructions, or Windsurf rules.
What Should Go in a CLAUDE.md File
Decide what belongs in CLAUDE.md and what belongs in the README, a path-scoped rule, or a skill. One test per line, applied to a real file.
Claude Code Is Not Following CLAUDE.md — How to Fix It
Diagnose why Claude Code ignores your CLAUDE.md: the file never loaded, the rule is vague, two files contradict, or the rule needs a hook instead.
CLAUDE.md vs .claude/rules vs Skills — Which File Owns What
Route each instruction to the right file: always-loaded CLAUDE.md, path-scoped .claude/rules/, or on-demand skills. One question decides it.
CLAUDE.md Best Practices Checklist — Audit Your File Against 8 Rules
Run your CLAUDE.md through eight checks: size, specificity, exact commands, anti-patterns, structure, contradictions, enforcement, and staleness.
Desk gear for long writing sessions
A few things that help if you write docs, tickets, and specs on a laptop all day.
Anker 5-in-1 USB-C Hub
One cable turns a laptop into a desk setup. Drives a 4K display, charges at up to 85W, and adds three data ports.
- 4K HDMI output
- 85W max power delivery
- 1x USB-C + 2x USB-A, 5Gbps each
- MacBook Pro, MacBook Air, Dell
Dell 27" S2725QC 4K
The monitor I write and review documents on. 163 PPI keeps small text sharp, and USB-C carries video and power on one cable.
- 3840x2160 IPS, 163 PPI
- 120Hz, 4ms, FreeSync Premium
- 99% sRGB
- USB-C, HDMI, DisplayPort
Apple MacBook Neo 13" (A18 Pro)
The cheapest way into an Apple-silicon machine that runs local models. Fanless, and the Liquid Retina panel holds small text at a full day of reading.
- A18 Pro chip, built for Apple Intelligence
- 8GB unified memory, 256GB SSD
- 13-inch Liquid Retina display
- 1080p FaceTime HD camera
Amazon affiliate links. We earn a commission on qualifying purchases at no extra cost to you.