CLAUDE.md is the instruction file that Claude Code loads at the start of every session. It lives in the repo root or in .claude/. It tells the agent the stack, the commands, the file boundaries, and the rules. Every line is sent on every turn, so the file should be short and specific.

What should a CLAUDE.md contain?

Name the project and stack. List the build, test, and deploy commands. Name the folders the agent may and may not edit. State the style rules and the do-not rules. Skip general advice the model already knows. This reviewer flags the lines that cost tokens without changing behavior.

CLAUDE.md vs AGENTS.md: what is the difference?

CLAUDE.md is read by Claude Code. AGENTS.md is the open convention read by OpenAI Codex and many other agents. The content overlaps almost fully. Review the file here, then use the CLAUDE.md Converter to produce AGENTS.md, .cursorrules, Copilot instructions, or Windsurf rules.

How do I review a CLAUDE.md for token waste?

Paste the file into the reviewer and run the audit. It looks for vague rules, duplicate advice, missing commands, missing repo boundaries, and paragraphs that cost tokens every Claude Code turn without changing behavior.

What should a good CLAUDE.md include?

A strong CLAUDE.md usually names the project, stack, key commands, file boundaries, test/deploy workflow, style conventions, and concrete do/don't rules. Short, enforceable rules work better than generic advice.

Can this help with AGENTS.md or Cursor rules?

Yes. Review the rules first, then use the CLAUDE.md Converter to turn the cleaned instructions into AGENTS.md, .cursorrules, Copilot instructions, or Windsurf rules.

Does the tool rewrite my entire CLAUDE.md?

No. It returns a numbered audit and a few targeted rewrite suggestions so you can decide what to keep. That is safer than blindly replacing your repo instructions.

Is my CLAUDE.md stored?

Your CLAUDE.md is sent to MarkdownMe's capped AI endpoint to generate the review. You choose whether we keep it to improve the tools. See the privacy page.

CLAUDE.md Reviewer

Claude Code reads your CLAUDE.md every session, so every vague or unused line costs tokens and weakens behavior. Paste your CLAUDE.md and get a numbered audit: missing commands, missing file boundaries, generic rules, over-long explanations, contradictions, and 1-3 rewritten paragraphs you can drop in directly. Need to create one from scratch? Use the CLAUDE.md generator. Continue into AGENTS.md, Cursor, Copilot, and Windsurf formats with the related converter.

After the review, convert the file with the CLAUDE.md Converter for AGENTS.md or Cursor.

AI-powered. Your CLAUDE.md is reviewed by MarkdownMe's capped AI endpoint. No login. Daily-capped to stay free.

Start with a common CLAUDE.md audit

Use an example shape, then replace it with your real repo instructions before reviewing.

CLAUDE.md reviewer guides

Use these examples when you need to cut token waste, add missing commands, tighten repo boundaries, or convert clean rules to other agent formats.

Token WasteFind vague, repeated, or unused CLAUDE.md instructions that cost tokens every Claude Code turn without improving behavior.CommandsCheck whether a CLAUDE.md includes the build, test, lint, dev server, deploy, and verification commands an agent needs before editing.BoundariesWrite CLAUDE.md rules that tell agents which files to edit, which files to avoid, and how to handle dirty worktrees safely.Convert After ReviewClean a CLAUDE.md first, then convert it into AGENTS.md, Cursor rules, GitHub Copilot instructions, or Windsurf rules.What BelongsDecide 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.Not FollowedDiagnose 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.Rules vs SkillsRoute each instruction to the right file: always-loaded CLAUDE.md, path-scoped .claude/rules/, or on-demand skills. One question decides it.Best PracticesRun your CLAUDE.md through eight checks: size, specificity, exact commands, anti-patterns, structure, contradictions, enforcement, and staleness.

Paste your CLAUDE.md

0 / 20,000 chars

Review & suggestions

What gets reviewed

• Missing sections (commands, file structure, conventions)
• Vague or generic instructions
• Over-long explanations that waste tokens per turn
• Missing behavioral rules (do X only, don't do Y)
• Inconsistencies and contradictions
• Returns numbered suggestions + 1-3 rewritten paragraphs

Inputs to AI tools may be used to improve MarkdownMe. Data controls

Studying for the Claude Certified Developer exam? Try 20 free CCDV-F practice questions.

Was this rewrite usable?

Get new tools by email

We add tools most weeks. Give an email address and we send you the new ones, plus short notes on how to use them. No more than one email a week. Unsubscribe with one click.

Common Workflows

Use these patterns when you need this tool for a real publishing, documentation, or developer workflow.

Audit a bloated CLAUDE.md for token waste

Claude Code users whose project instructions have grown into vague, repetitive, or expensive context.

Paste the existing CLAUDE.md
Review missing sections, vague rules, and token-waste notes
Apply the suggested paragraph rewrites manually

A tighter agent instruction file that costs fewer tokens and gives clearer coding behavior.

Search intent: review CLAUDE.md for token waste

Improve agent behavior rules before a coding session

Teams using Claude Code, Codex, Cursor, or similar agents that need concrete project rules.

Paste the current agent instruction file
Look for missing commands, file boundaries, and do-not-do rules
Copy the strongest rewrite suggestions into the file

A more actionable CLAUDE.md that tells the agent how to work in the repo.

Search intent: improve Claude Code CLAUDE.md instructions

Review generated CLAUDE.md before committing

Developers who generated a first draft and want a second pass before checking it into the repo.

Generate or paste the CLAUDE.md draft
Run the reviewer
Keep only the concrete rules and remove generic filler

A commit-ready instruction file with fewer vague rules.

Search intent: CLAUDE.md reviewer for Claude Code

Convert cleaned Claude Code instructions to other agent formats

Developers who want one source of repo rules for Claude Code, Codex, Cursor, GitHub Copilot, and Windsurf.

Review the CLAUDE.md for vague or duplicate instructions
Apply the concrete fixes
Open the CLAUDE.md Converter and generate AGENTS.md, .cursorrules, or Copilot instructions

A cleaned instruction source that can be reused across multiple AI coding assistants.

Search intent: CLAUDE.md to AGENTS.md after review

Example Input and Output

A short CLAUDE.md with three common problems

CLAUDE.md

# Project

This is a Next.js app. Please write clean, well-documented code and follow best practices.

Run tests before committing.

The backend lives in /backend and uses Python.

Audit

1. Missing commands. "Run tests before committing" names no command. Add: `npm test` for the frontend, `pytest backend/` for the API.
2. Vague rule. "Write clean, well-documented code and follow best practices" costs tokens every turn and changes nothing. Delete it.
3. Missing boundary. /backend is named but not fenced. Add: "Never edit backend/migrations/ by hand; run `alembic revision`."

Rewritten paragraph:
## Commands
- Frontend tests: `npm test`
- API tests: `pytest backend/`
- Never edit backend/migrations/ by hand; run `alembic revision`.

The audit numbers each finding, names the cost (tokens, a missing command, an unfenced directory), and ends with a paragraph you can paste in.

How to Use CLAUDE.md Reviewer

Open the CLAUDE.md Reviewer
Choose an example audit shape or paste your real CLAUDE.md
Run the AI review
Apply the numbered suggestions that match your repo
Convert the cleaned instructions to AGENTS.md, Cursor rules, Copilot instructions, or Windsurf rules if needed

Frequently Asked Questions

What is CLAUDE.md?: CLAUDE.md is the instruction file that Claude Code loads at the start of every session. It lives in the repo root or in .claude/. It tells the agent the stack, the commands, the file boundaries, and the rules. Every line is sent on every turn, so the file should be short and specific.
What should a CLAUDE.md contain?: Name the project and stack. List the build, test, and deploy commands. Name the folders the agent may and may not edit. State the style rules and the do-not rules. Skip general advice the model already knows. This reviewer flags the lines that cost tokens without changing behavior.
CLAUDE.md vs AGENTS.md: what is the difference?: CLAUDE.md is read by Claude Code. AGENTS.md is the open convention read by OpenAI Codex and many other agents. The content overlaps almost fully. Review the file here, then use the CLAUDE.md Converter to produce AGENTS.md, .cursorrules, Copilot instructions, or Windsurf rules.
How do I review a CLAUDE.md for token waste?: Paste the file into the reviewer and run the audit. It looks for vague rules, duplicate advice, missing commands, missing repo boundaries, and paragraphs that cost tokens every Claude Code turn without changing behavior.
What should a good CLAUDE.md include?: A strong CLAUDE.md usually names the project, stack, key commands, file boundaries, test/deploy workflow, style conventions, and concrete do/don't rules. Short, enforceable rules work better than generic advice.
Can this help with AGENTS.md or Cursor rules?: Yes. Review the rules first, then use the CLAUDE.md Converter to turn the cleaned instructions into AGENTS.md, .cursorrules, Copilot instructions, or Windsurf rules.
Does the tool rewrite my entire CLAUDE.md?: No. It returns a numbered audit and a few targeted rewrite suggestions so you can decide what to keep. That is safer than blindly replacing your repo instructions.
Is my CLAUDE.md stored?: Your CLAUDE.md is sent to MarkdownMe's capped AI endpoint to generate the review. You choose whether we keep it to improve the tools. See the privacy page.

Claude Code tools

One CLAUDE.md, reviewed, generated, converted, and costed. Start at the hub for the guides.

CLAUDE.md generator — Create a CLAUDE.md from your stack, commands, and conventions.
CLAUDE.md to AGENTS.md converter — The same instructions for Codex, Cursor, Copilot, and Windsurf.
All Claude Code tools — The hub: every CLAUDE.md tool and guide on one page.

Related Tools

CLAUDE.md Converter

Convert agent configs between CLAUDE.md, AGENTS.md, .cursorrules, .github/copilot-instructions.md, and .windsurfrules. One file, every format.

CLAUDE.md Generator

Describe your project in 1-2 sentences and get a structured CLAUDE.md. AI-powered. Free, no login.

AI Prompt Optimizer (Rewrites Your Prompt)

Paste a rough prompt and get a structured, production-grade rewrite — Role, Context, Task, Constraints, Output Format, and Examples — tuned to best practices from Anthropic, OpenAI, and Google. AI-powered.

Link Extractor

Extract all URLs and links from Markdown text. Free online Markdown link extractor.

About CLAUDE.md Reviewer

Paste your existing CLAUDE.md and get specific, numbered suggestions for vague rules, missing commands, repo boundaries, and token waste. This AI-backed tool sends your input to MarkdownMe's capped AI endpoint to generate the result. You choose whether we keep it to improve the tools. See the privacy page. No account is required. MarkdownMe provides free, fast, and reliable Markdown tools for developers, writers, and anyone who works with Markdown.