claude-code-hooks-daemon
CLAUDE.md4 starsChanged 16 days agoMITView on GitHub
Single Source of Truth: the documentation-SSoT rules live in CLAUDE/DocumentationStrategy.md; the table below routes each human-docs topic to its canonical file. When adding new content: put it in the canonical file and add a link from any other file that needs to mention it. Do not copy-paste the content.
In this repository14 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- CLAUDE/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- acceptance-testSkill
- configureSkill
- docs-optimiseSkill
- docs-qaSkill
- hooks-daemonSkill
- issue-sdlcSkill
- modeSkill
- releaseSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
When adding new content: put it in the canonical file and add a link from any other file that needs to mention it.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SSOT Rule for docs/
Single Source of Truth: the documentation-SSoT rules live in CLAUDE/DocumentationStrategy.md; the table below routes each human-docs topic to its canonical file.
| Topic | Canonical Source |
| Per-handler options, values, defaults | docs/guides/HANDLER_REFERENCE.md |
| Configuration format & structure | docs/guides/CONFIGURATION.md |
| Installation & first-use | docs/guides/GETTING_STARTED.md |
| Troubleshooting | docs/guides/TROUBLESHOOTING.md |
| QA suite (human overview) | docs/QA.md |
| Plan system (human overview) | docs/PLAN_SYSTEM.md |
| Vendoring remote docs (human guide) | docs/guides/REMOTE_DOCS.md |
| Claude Code plugins beside the daemon | docs/guides/CLAUDE_CODE_PLUGINS.md |
| Subagent model tiers (human guide) | docs/guides/SUBAGENT_MODEL_TIERS.md |
When adding new content: put it in the canonical file and add a link from any other file that needs to mention it. Do not copy-paste the content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.