learn-evallisted

# /learn-eval - Extract, Evaluate, then Save Extract a reusable pattern from the session, gate it, and route every Save to a destination something actually reaches. ## What to Extract Look for: 1. **Error Resolution Patterns** — root cause + fix + reusability 2. **Debugging Techniques** — non-obvious steps, tool combinations 3. **Workarounds** — library quirks, API limitations, version-specific fixes 4. **Project-Specific Patterns** — conventions, architecture decisions, integration patterns ## Process 1. Review the session for extractable patterns 2. Identify the most valuable/reusable insight 3. **Determine the destination — there is no parking lot.** Every Save must land somewhere that something actually routes to (ADR-0047), so pick one of exactly two: - **Absorb into an existing asset** — the pattern belongs inside a skill, rule, or `hooks/README.md` section that already owns the topic. Name the file and the section. This is the default: an addition to a reachable asset beats a new file. - **Promote to a skill** — the pattern has its own independent trigger (a user request that no installed skill answers). Run skill: **skill-creator** (required by `rules/common/skills.md` before writing any skill). If neither fits, the verdict is **Drop**, not "park it somewhere for now". A note that nothing points at is reachable only by grep, and grep requires already knowing the content exists — measured over 74 days, the retired `lea