ultramemory-snapshotlisted

# UltraMemory session snapshot Install: copy this file to `~/.claude/skills/ultramemory-snapshot/SKILL.md` (`mkdir -p ~/.claude/skills/ultramemory-snapshot && cp -r skills/ultramemory-snapshot ~/.claude/skills/`). It is invoked automatically by the every-Nth-turn nudge from `hooks/capture-hook.sh` (cadence `ULTRAMEMORY_SNAPSHOT_EVERY`, default 5), or any time you decide the session is worth snapshotting. ## What to write Write exactly **one rich card** — a self-contained narrative of ~40–120 words — that captures the durable substance of the work in this order: 1. **Blocker** — the concrete problem you were solving. 2. **Approaches tried** — what you attempted, including the ones that failed. 3. **What worked** — the fix / decision that resolved it. 4. **How it was verified** — the exact test, command output, version, or metric that proves it. ## Fidelity — the wayback test Write so a reader with **zero context, months from now**, fully understands it: - **Named entities, never pronouns** — "the OrderService retry bug", not "it" or "this". - **Absolute dates only**, resolved against today's real date — "on 2026-07-04", never "today", "yesterday", or "last week". - **Fold in the concrete substance** — exact commands, error strings, versions, file paths, ids, numbers, URLs. - **Never a bare** "true"/"false"/"yes"/"done" — fold the substance into the value instead. - Keep a short supporting quote from the session in `rationale` (under ~200 characters). ## BAD vs GOOD