EveryIncCLAUDE.mdcompounding-engineering-plugin
EveryInc/compounding-engineering-plugin/CLAUDE.md
No summary in the file. Open it to read it.
169 projects use a version of this
CLAUDE.md examples from real projects
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Your trail
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.
Worked for most · soon
EveryIncCLAUDE.mdEveryIncCLAUDE.mdhands-on-deck
EveryInc/hands-on-deck/CLAUDE.md
Any change to the skill — skills/hands-on-deck/SKILL.md, deck.py, the docs it ships, or its behavior — must bump the version in the same PR. Two files carry it and they move together: (Leave marketplace.json's top-level metadata.version alone — that's the marketplace's own version, not the plugin's.) Follow semver and the existing commit convention: Commit message format: hands-on-deck X.Y.Z: <one-line summary of the change>.
EveryIncCLAUDE.mdgarbage-man
EveryInc/garbage-man/CLAUDE.md
For installation and usage requests, follow plugins/email-cleaner/skills/email-cleanup/SKILL.md. Use a native email connector when one is available. Otherwise offer the read-only IMAP adapter or canonical JSONL ingestion. Keep credentials out of chat and keep mailbox data in .mailroom/.
About CLAUDE.md
What is CLAUDE.md?
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
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.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.