What problem does it solve? Hard-won debugging insights and design decisions evaporate when a work session ends, forcing every future session to re-investigate the same problems from scratch. This Skill captures those learnings as durable, searchable documentation so each unit of engineering work makes the next one easier. ## Core Features & Use Cases - Solution Capture: Writes one markdown file per learning to docs/solutions/<category>/ with a structured template covering problem, root cause, solution, and prevention. - Grounding Check: Searches docs/solutions/ with grep before investigating a bug, so already-solved problems are found instead of re-derived. - Capture Discipline: Defines clear rules for what to document (non-obvious root causes, durable decisions) versus what to skip (typos, unverified fixes, anything git history already covers). - Use Case: After spending hours tracing a multi-tenant database scoping bug, document the root cause and fix in docs/solutions/database-issues/ so the next session that hits a similar symptom finds the answer in minutes. ## Quick Start Document the root cause and fix for the bug we just solved as a new entry in docs/solutions so future sessions can find it.