How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
AnthropicCLAUDE.mdanthropics/launch-your-agent/CLAUDE.md
patterns + typical endpoint schemas — so v1 is just the swap to the real MCP server + vault. - **Voice**: warm welcome, no clinical process talk, no time estimates or unverified durations; compact/dense
hoangsonwwCLAUDE.mdhoangsonww/Claude-Code-Agent-Monitor/CLAUDE.md
printed command, surfaced in the UI and by `ccam update-check`.) - `mcp/`: local MCP server exposing dashboard operations as tools. ## Non-negotiable engineering rules - Preserve existing behavior unless explicitly asked
bytechefhqCLAUDE.mdbytechefhq/bytechef/CLAUDE.md
both `com.fasterxml.jackson` and `tools.jackson` packages currently appear in deps), SpringDoc OpenAPI 3.0.3 ### Main Server Module Structure #### Core Modules (`server/libs/`) - **`atlas/`** - Workflow engine core - `atlas-coordinator/` - Orchestrates workflow execution - `atlas-execution
MadAppGangCLAUDE.mdMadAppGang/claudish/CLAUDE.md
write | Means | |---|---|---| | harness | host | Claude Code driving the session; "host" is the MCP host that spawns the server | | foreign model | external model | any model not native to the harness
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
