capture-practicelisted

# Capture Practice Register an insight, pattern, or lesson learned in the dotforge inbox. ## Input routing **If $ARGUMENTS is empty → auto-detect mode (Step 0).** **If $ARGUMENTS has content → skip to Step 1.** --- ## Step 0: Auto-detect (only when $ARGUMENTS is empty) Analyze the recent conversation to identify the most generalizable insight from this session. ### Detection signals (in priority order) 1. **Workaround discovered** — the obvious approach failed and an alternative was used 2. **Multi-attempt bug** — a fix required more than one attempt or root cause was non-obvious 3. **Architectural decision with trade-offs** — two+ alternatives were considered, one chosen with reasoning 4. **Non-obvious tool/API/flag behavior** — a parameter, edge case, or behavior was surprising 5. **Missing rule** — the session revealed a gap in `.claude/rules/` or `CLAUDE.md` that would have prevented the problem ### Extraction rules - Extract the single most generalizable insight — not session notes, not a summary of everything done - Formulate it as a reusable principle: "When X, do Y because Z" or "Never do X — use Y instead" - Keep it to 1-2 sentences max - Ignore: trivial tasks, first-attempt successes, routine edits ### If no signal is present Respond: "No generalizable insight detected in this session. If you have something specific in mind, run `/cap \"description\"`." Stop — do not create a file. ### Propose and confirm Show the proposed insight and ask for confirmat