How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
ComposioHQCLAUDE.mdComposioHQ/composio/CLAUDE.md
Claude Code compatibility shim. Use AGENTS.md for repository guidance. Local skills are canonical under .agents/skills; .claude/skills points there for Claude-compatible clients.
Steady16 mentions in 2 weeks
No other project uses it yet
ComposioHQCLAUDE.mdComposioHQ/composio/docs/CLAUDE.md
Claude Code compatibility shim. Use docs/AGENTS.md for documentation-site guidance. Docs-agent context lives in docs/agent-guidance/, and neutral decisions live in docs/decisions/.
Steady16 mentions in 2 weeks
No other project uses it yet
ComposioHQCLAUDE.mdComposioHQ/agent-orchestrator/CLAUDE.md
Read and follow AGENTS.md for repository layout, commands, coding conventions, and hard rules. All app state, the daemon's data dir, running.json, worktrees, and the Electron supervisor's userData (Chromium cache, cookies, local/session storage, crash dumps), must resolve under ~/.ao (overridable via AODATADIR/AORUNFILE). Never write AO state to ~/Library/Application Support or any other OS-default app-data location. The sole read exception is an explicit user-initiated import from a validated Chrome, Firefox, or Safari profile: read known source files without modifying them and keep…
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.
