mycelium
CLAUDE.md1 starsChanged 3 months agoMITView on GitHub
This repo runs a local Mycelium Core (http://127.0.0.1:8787) that provides RAG-scoped, token-budgeted context — the same chunk/embed/retrieve/budget-assemble pipeline used by services/core/src/mycelium/core/domain/chatassembler.py and ragservice.py, but applied to the coding session itself instead of the chat product. Use it instead of broad grepping or dumping whole files. - At the start of meaningful work, call myceliumsessionstart (or myceliumpreflight for lighter exploration) with the absolute workspace path. It returns a compact bootstrap packet plus a one-line receipt — cite the receipt, don't re-fetch…
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Before planning or building anything new, call mycelium_reuse_check(goal) first — it checks for prior art across all indexed repos.
- Very specific: line 16
Prefer mycelium_change_context(goal) when implementing, mycelium_debug_context(error) when fixing, and mycelium_search(query) for general …
- Distinctive: line 18
Do not dump chat transcripts into the vault, and do not paste full files when a receipt already covers the hit list.
- Very specific: line 21
If mycelium_health reports the Core is unreachable, fall back to normal exploration (Explore agent / grep) rather than blocking on it.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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
MemoryOptimization
Mycelium context layer (required)
This repo runs a local Mycelium Core (http://127.0.0.1:8787) that provides RAG-scoped,
token-budgeted context — the same chunk/embed/retrieve/budget-assemble pipeline used by
services/core/src/mycelium/core/domain/chat_assembler.py and rag_service.py, but applied
to the coding session itself instead of the chat product. Use it instead of broad grepping
or dumping whole files.
- At the start of meaningful work, call
mycelium_session_start(ormycelium_preflightfor lighter exploration) with the absolute workspace path. It returns a compact bootstrap packet plus a one-line receipt — cite the receipt, don't re-fetch the full vault/code. - Before planning or building anything new, call
mycelium_reuse_check(goal)first — it checks for prior art across all indexed repos. If it says to ask the user reuse-vs-new, ask and wait. - Prefer
mycelium_change_context(goal)when implementing,mycelium_debug_context(error)when fixing, andmycelium_search(query)for general lookups — over grepping or globbing many files. - Do not dump chat transcripts into the vault, and do not paste full files when a receipt already covers the hit list.
If mycelium_health reports the Core is unreachable, fall back to normal exploration (Explore
agent / grep) rather than blocking on it.
In this repository46 other files it gives its agents.
- bmad-advanced-elicitationSkill
- bmad-agent-analystSkill
- bmad-agent-architectSkill
- bmad-agent-devSkill
- bmad-agent-pmSkill
- bmad-agent-tech-writerSkill
- bmad-agent-ux-designerSkill
- bmad-architectureSkill
- bmad-brainstormingSkill
- bmad-check-implementation-readinessSkill
- bmad-checkpoint-previewSkill
- bmad-code-reviewSkill
- bmad-correct-courseSkill
- bmad-create-architectureSkill
- bmad-create-epics-and-storiesSkill
- bmad-create-prdSkill
- bmad-create-storySkill
- bmad-customizeSkill
- bmad-dev-autoSkill
- bmad-dev-storySkill
- bmad-document-projectSkill
- bmad-domain-researchSkill
- bmad-editorial-review-proseSkill
- bmad-editorial-review-structureSkill
- bmad-edit-prdSkill
- bmad-forge-ideaSkill
- bmad-generate-project-contextSkill
- bmad-helpSkill
- bmad-index-docsSkill
- bmad-market-researchSkill
- bmad-party-modeSkill
- bmad-prdSkill
- bmad-prfaqSkill
- bmad-product-briefSkill
- bmad-qa-generate-e2e-testsSkill
- bmad-quick-devSkill
- bmad-retrospectiveSkill
- bmad-review-adversarial-generalSkill
- bmad-review-edge-case-hunterSkill
- bmad-shard-docSkill
- bmad-specSkill
- bmad-sprint-planningSkill
- bmad-sprint-statusSkill
- bmad-technical-researchSkill
- bmad-uxSkill
- bmad-validate-prdSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

