reflectlisted

# Reflect — promote staged learnings safely You are folding the project's recent experience into its durable memory. This is the review gate that keeps auto-capture honest: **nothing becomes a rule without your judgment, and every change is reversible.** ## Inputs - `.claude/knowledge/pending.md` — candidates staged by the `SessionEnd` hook (each a `###` entry tagged `HIGH`/`MED`). - The current conversation (additional corrections the hook may have missed). ## Procedure 1. **Read** `pending.md` and skim the recent conversation. Build a list of candidate learnings. 2. **Judge each candidate** against three tests — keep only if it passes all: - **Specific** — names a concrete behavior, file, command, or convention (not "write good code"). - **Reusable** — will matter again in future sessions, not a one-off for this task. - **Actionable** — you can phrase it as a directive the next session can follow. Default to **rejecting** when unsure — a wrong rule is worse than a missing one. 3. **Deduplicate**: if a candidate restates something already in `core-rules.md` / `conventions.md`, skip it (or tighten the existing entry instead of adding a new one). 4. **Route** each surviving learning to exactly one home: - Behavior directive / "always|never" → `.claude/rules/core-rules.md` → **Learned rules**. - Project naming/pattern/anti-pattern → `.claude/knowledge/conventions.md`. - A gotcha + its fix → `.claude/knowledge/bugs-and-fixes.md` (one table row