snapshotlisted

# Snapshot Two modes. Pick one before doing anything else. | Mode | Use when | Result | |---|---|---| | **save** (default) | About to clear, compact, close the laptop, or hand off | `snapshots/snapshotN.md` written in the current project | | **brief** | Fresh context, resuming work, "where were we" | One orientation message, verified against reality | ## When to use this **save** — "snapshot", "snapshot this", "save progress", "save state", "before I clear", "I'm about to clear", "write it down before we lose it", end of a working session. **brief** — "brief me", "catch up", "where were we", "get back up to speed", "read the snapshot", or a `/snapshot` with no prior conversation to save. **If the mode is genuinely ambiguous, ask.** One question, then proceed. Do not guess and write a file — a snapshot built from an empty context is worse than none. **Do not use this for:** the durable project record. That is the project's long-lived doc — `HANDOFF.md`, `CONTRIBUTING.md`, an architecture doc, whatever the project keeps. A snapshot is volatile working memory: where the cursor is *right now*. The long-lived doc is what the project *is*. Where this skill says `HANDOFF.md`, read it as "the project's durable doc, if it has one". | Snapshot (volatile) | Durable project doc | |---|---| | What I am mid-way through | Shipped features | | The next concrete action | Live URLs, ports, infra IDs | | This session's files and decisions | Architecture decisions | | Open questions for