compound-knowledgelisted

# Compound Knowledge Every hard-won fix that only lives in one session's context gets re-derived from scratch the next time it comes up — in a different session, by a different agent, or by the same agent six months later with no memory of last time. This skill turns a solved problem into a searchable artifact so the investigation compounds instead of repeating. ## When to use this - **Capture** right after closing out a problem that took genuine investigation: a non-obvious root cause, a workaround for a library/platform quirk, a gotcha that will plausibly bite again. Not "fixed a typo" — that doesn't need a doc. - Triggered by the user saying "that worked," "remember this," or on your own initiative right after verifying a hard-won fix (see [`verify-before-done`](../verify-before-done) — don't document a fix you haven't actually confirmed works). - **Search** before starting non-trivial debugging or investigation — check `docs/solutions/` first in case this was already solved. ## Instructions ### Capturing a solution 1. **Confirm it's actually solved.** Don't write up a fix you're only hoping works — verify it per `verify-before-done`'s evidence ladder first. 2. **Check for a near-duplicate first.** Search `docs/solutions/` by keyword/category — if this updates or extends an existing doc rather than being genuinely new, update that file instead of creating a near-duplicate. 3. **Pick a category** from a small fixed set so the folder stays scannabl