capture-rulelisted

# Capture Rule Route durable knowledge to the home where it will auto-inject when next relevant. ## Step 1 — Qualify the insight Capture only knowledge that is **reusable** and **non-obvious from code, git history, or existing instruction files**: gotchas, build/tooling quirks, design invariants, conventions, the "why" behind a decision. Skip (and tell the user why) if it is: a one-off fact for this task only, already documented in the repo, or plainly derivable by reading the code. If it does not qualify, stop here. Establish the **target repository** the insight is about. If unclear, infer from the files touched this session and confirm with the user. ## Step 2 — Route to a home Pick exactly one: | Insight is about… | Home | |---|---| | A specific repo's own code/tooling | that repo's `.claude/rules/<slug>.md` | | Target-repo files, but the rule must live in the harness workspace | harness `.claude/rules-ex/<slug>.md` | | The harness's own machinery | harness `.claude/rules/<slug>.md` (often grow the internals notes file, e.g. `harness-internals.md` or `vault-harness.md`) | | Personal/cross-project preference, feedback, or machine-local fact | auto-memory (`MEMORY.md` + `memory/`) | If the home is auto-memory, do **not** write a rule — tell the user it belongs in memory and stop. ## Step 3 — Dedup Search the chosen directory for an existing rule on the same topic. If one exists, **update it** instead of creating a new file. One topic = one file. ## Step 4 — Writ