compile-knowledgelisted

# compile-knowledge Durable knowledge is worth keeping as many small, interlinked markdown files, compiled over time and surfaced through an index — not as one giant doc, a chat log, or a one-off file that rots. This skill makes compiling consistent so your agent gets smarter over time instead of relearning the same things. ## Where it goes — pick the right store - **Agent memory** (default, always available): your `.claude/.../memory/` folder with `MEMORY.md` as the index. This is the per-agent store and it survives restarts — it's the karpathy "external memory" that keeps you sharp across sessions. Governed by the memory rules already in your system prompt — follow them. For most agents this is the only store you need. - **Shared wiki** (only if you work as a team): a `wiki/` folder in your project with a `wiki/index.md`. For knowledge the *whole team* benefits from — domain facts, research findings, reference material multiple agents would re-derive. Skip this entirely if you're a solo agent; don't manufacture team ceremony. Rule of thumb: "only I act on this" → memory. "Anyone on my team might need this" → shared wiki. Cross-link between them with `[[slug]]` when they relate. ## Before you write — the hygiene gate Compile ONLY a durable, non-obvious fact. Skip and move on if it is: - routine / derivable from the repo, git history, or existing docs, - true only for this one conversation, - already covered by an existing file (→ UPDATE that file instead,