kb-wiki-uselisted

# KB Wiki — Use as persistent knowledge base The wiki at `wiki/` is the primary long-term memory store for this project. Claude reads it to orient and writes whenever something worth preserving is learned or decided. ## When to READ (proactive) - **Session start** — `wiki/brain.md` HEAD first, then targeted lookups via `kb_search` (MCP); fallback to `wiki/index.json` by `importance_score` when the MCP is unavailable. - **Project question / concept reference / about to implement / about to edit a wiki page** — search wiki first via `kb_search`; load 1-3 specific pages prioritised by the returned RRF score. - **Time-sensitive flags** — note staleness risks in any answer drawing on flagged content. ## When to WRITE (proactive) Write when a significant decision is made, a non-obvious pattern is discovered, a lesson is worth preserving, a new concept/module/integration is added, the user says *"remember this"* / *"document this"*, or a task meaningfully changes how the project works. Do NOT write for: ephemeral task state, content fully derivable from code, short-term decisions likely to be reversed, content already covered (update instead). ## Decision flow ``` Worth preserving → Glob wiki/**/*.md for the topic ├── No match → kb-wiki-create ├── Match, info missing → kb-wiki-update └── Match, info present → skip ``` Use the named operational skills (`kb-wiki-create`, `kb-wiki-update`, `kb-wiki-deprecate`) for the actual write — they enforce frontmatter, Summary,