claude-life-agent / 30_KNOWLEDGE
CLAUDE.md2 starsChanged 4 months agoMITView on GitHub
What you've learned and what the agent has researched for you. This is [AI] territory: analysis, research output, reference material. Keep it separate from [OWNER] decisions in 00_SELF/decisions/. 배운 것과 에이전트가 리서치한 것. [AI] 영역: 분석·리서치 결과·참고자료. 00_SELF/decisions/의 [OWNER] 결정과 분리. - Tag research [AI]. It informs decisions; it doesn't make them. - When the agent produces a finished deliverable you'll actually read, keep three things together: the file, a short .md summary (so it's searchable), and a one-line entry…
In this repository9 other files it gives its agents.
- 00_SELF/CLAUDE.mdCLAUDE.md
- 10_WORK/CLAUDE.mdCLAUDE.md
- 20_DOMAINS/CLAUDE.mdCLAUDE.md
- 40_SYSTEMS/CLAUDE.mdCLAUDE.md
- 50_LIFE/CLAUDE.mdCLAUDE.md
- 90_SHARED/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- addSkill
- sttSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
When the agent produces a finished deliverable you'll actually read, keep three things together: the file, a short .md summary (so it's …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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
30_KNOWLEDGE — research & knowledge
What you've learned and what the agent has researched for you. This is
[AI]territory: analysis, research output, reference material. Keep it separate from[OWNER]decisions in00_SELF/decisions/.배운 것과 에이전트가 리서치한 것.
[AI]영역: 분석·리서치 결과·참고자료.00_SELF/decisions/의[OWNER]결정과 분리.
Suggested layout
30_KNOWLEDGE/
├── research/ # deep-dives, analysis the agent produced (working material, [AI])
├── documents/ # finished reports you actually read (with a .md summary + an INDEX)
└── reference/ # durable reference notesRules
- Tag research
[AI]. It informs decisions; it doesn't make them. - When the agent produces a finished deliverable you'll actually read, keep three things
together: the file, a short
.mdsummary (so it's searchable), and a one-line entry in anINDEX.md. A PDF alone isn't findable later; the summary is. - Analysis docs and proposal/plan docs stay separate.
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.

