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.
garrytanReads credentialsCLAUDE.mdgarrytan/gstack/CLAUDE.md
headless-browser CLI (the fallback engine) plus the `/browse` skill, `design/` design binary, `make-pdf/` PDF binary, `hosts/` typed host configs, `scripts/` build+DX tooling (gen-skill-docs, resolvers — `resolvers/aside.ts
Steady23 mentions in 2 weeks
No other project uses it yet
browser-useCLAUDE.mdbrowser-use/browser-use/CLAUDE.md
Browser Management BrowserSession uses a `bubus` event bus to coordinate watchdog services: - **DownloadsWatchdog**: Handles PDF auto-download and file management - **PopupsWatchdog**: Manages JavaScript dialogs and popups - **SecurityWatchdog**: Enforces domain restrictions
Steady7 mentions in 2 weeks
1 project uses a version of this
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.
