Guides · Free tool · runs in your browser · no signup

CLAUDE.md checker

Paste your CLAUDE.md and get a 0–100 score with specific fixes — graded against the same best practices the annotated example and field guide teach. Everything runs locally; nothing you paste is uploaded or stored.

What a high-scoring CLAUDE.md gets right

CLAUDE.md is loaded into every Claude Code session, so it earns its place by being concrete and short. The checker grades eight things that separate a CLAUDE.md the agent can act on from one it mostly ignores:

• Real commands. The exact install / dev / test / build commands, in backticks, so the agent runs yours instead of guessing.
• Test discipline. An explicit "run the tests and confirm they pass before calling a task done" beats "write good tests."
• Guardrails. A short "Do not" list — don't touch generated files, don't commit to main, secrets come from .env — prevents the most common mistakes.
• Where code lives. A few lines on architecture so the agent puts new code in the right place.
• Sensible length. Under ~200 lines. It's loaded every session; every line costs tokens and dilutes the rules that matter.
• Scannable structure. Headings and bullets, not walls of prose.
• Specific, not vague. "Match the surrounding style" is actionable; "write clean code" is noise.

For the full walkthrough — load order, @imports, how it relates to AGENTS.md — see the annotated CLAUDE.md example. Building the rest of your setup? The guide library covers subagents, skills, slash commands, hooks, and MCP.

This is a heuristic linter, not a verdict — it checks structure and common gaps, and can't judge whether the facts in your file are correct. Use the findings as a checklist, then keep what fits your project.