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