What problem does it solve? Hard-won fixes, decisions, and patterns often die in chat logs or scratch files, forcing you to re-derive solutions you already found. This Skill captures each learning as a tagged, linked, provenance-backed note in the right home so you retrieve it in seconds instead of re-solving it in hours. ## Core Features & Use Cases - Structured knowledge nuggets: Each learning is stored with a 4-axis tag taxonomy, mandatory provenance (where, when, link), confidence level, status, and cross-links to related notes and index/hub notes. - Content-routed storage: Visual knowledge (teardowns, pattern boards) goes to Figma/FigJam; written knowledge (fixes, decisions, snippets) goes to Docs/Markdown, with one identical tag taxonomy across both homes. - Retrieve-before-rebuild gate: Before solving a problem or starting a build, query the knowledge base across tags and full-text; reuse hits, extend partials, and capture misses on the way out. - Use Case: After fixing a Next.js hydration mismatch, you file a tagged nugget with the commit link. Two months later, before wiring a theme toggle, a quick search surfaces the note and you apply the guard immediately instead of re-debugging. ## Quick Start Save this fix to my knowledge base with tags and a link to the commit so I can find it next time.
