What problem does it solve? After solving a non-trivial bug, design decision, or incident, the reasoning behind the fix disappears when the session ends. This Skill captures the trap, insight, and rule behind a solution into a version-controlled Markdown note so future sessions and engineers skip the same discovery process. ## Core Features & Use Cases - Structured learnings notes: Writes notes to docs/learnings/ with five mandatory sections — Problem, Trap, Insight, Rule, and a runnable Verify command. - Index maintenance: Updates docs/learnings/README.md with a one-line index entry for each new note. - Quality gates: Enforces one insight per note, requires concrete file paths that exist, and rejects trivial problems that lack a real insight. - Use Case: After diagnosing why 10 of 14 FastAPI routes returned 404 due to an indentation shift in a route registration function, run this Skill to record the trap, the insight about silent include_router behavior, and a grep-based verify command. ## Quick Start Ask the AI to extract the approach from the bug fix just completed and save it as a learnings note in docs/learnings/.