secretary
AgriciDaniel/secretary/CLAUDE.md
No summary in the file. Open it to read it.
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.
AgriciDaniel/secretary/CLAUDE.md
No summary in the file. Open it to read it.
AgriciDaniel/deepseek-harness-brain/CLAUDE.md
Claude-specific note: this file is persistent project context, not an enforcement layer. Release readiness is enforced by scripts/audit_brain.py and scripts/package_release.py.
AgriciDaniel/gauntlet-loop-brain/CLAUDE.md
Claude-specific note: this file is persistent project context, not an enforcement layer. Release readiness is enforced by scripts/audit_brain.py and scripts/package_release.py.
AgriciDaniel/agentic-habits/CLAUDE.md
Claude-specific note: this file is project context, not enforcement. What is actually enforced here is .github/checks.sh, .github/test-gate.sh, .github/test-install.sh and the CI workflow. A rule in none of them is a hint, which is the argument the package itself makes.
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.