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.
rush86999Reads credentialsCLAUDE.mdrush86999/atom/CLAUDE.md
register_server` (real handshake, replaces the placeholder), `api/mcp_client_routes.py` (`/api/mcp/servers`): Atom connects to arbitrary external MCP servers (Cloudflare "MCP Server Portals"), not just the 3 hardcoded pseudo-servers. 48. **Per-Canvas
ComposioHQReads credentialsCLAUDE.mdComposioHQ/trustclaw/CLAUDE.md
shadcn MCP** tools instead. ## Architecture This dashboard uses a **single tRPC backend** running within Next.js. Auth is handled by Better Auth with username/password. Composio functionality is accessed server-side using
pnpCLAUDE.mdpnp/powershell/CLAUDE.md
adding one. - **Skills**: `.claude/skills/` — `code-review`, `new-cmdlet`. Same arrangement. - **MCP**: `.mcp.json` configures the GitHub and Microsoft Learn servers. See [`.agents/README.md`](.agents/README.md). `docs-sync`, `permissions-auditor` and `api-surface-diff
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.
