Need AI Training/Help?CloudYeti.io/meet
MarkdownMe
… total tool calls on MarkdownMeStats →
All tools
Claude collection

Claude Code and CLAUDE.md tools

Your CLAUDE.md file shapes every Claude Code session. These tools help you review it for vague rules and token waste, generate one from scratch, and convert it to other agent formats. Free, no signup.

CLAUDE.md how-to guides

Step-by-step answers for writing, reviewing, and converting CLAUDE.md files.

CLAUDE.md FAQ

What is CLAUDE.md?

CLAUDE.md is a project instruction file that lives in a repository root and tells Claude Code what your project needs: build commands, testing rules, file boundaries, and conventions. Claude Code loads it in every session, so it shapes every interaction.

What should a CLAUDE.md contain?

Include the commands Claude needs: build, test, lint, dev server, and deploy. Add your project layout, naming conventions that differ from tool defaults, and two real anti-patterns your team has hit. Skip generic advice like write good code and follow existing patterns. Keep it under 200 lines.

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

CLAUDE.md is for Claude Code. AGENTS.md is the shared format that Codex and several other agents read. .cursorrules is for Cursor. They all tell an agent the same kinds of facts about your project, but they load in different editors. Many teams maintain one clean CLAUDE.md and generate the other formats from it.

Does a long CLAUDE.md cost tokens every turn?

Yes. Claude Code loads your CLAUDE.md into every session, so every line consumes tokens on every turn. That is why cutting vague rules and stale notes pays off: a 50-line file costs less than a 200-line file even when they say the same thing.

Working with Cursor instead? The CLAUDE.md Converter generates .cursorrules from your CLAUDE.md. For Copilot, Windsurf, or Codex, convert to those formats too.