claude-memlisted

# Claude-Mem — Memory Keeper > "Persistent memory" Chat context evaporates; files don't. Give every project a paper trail the next session can boot from. ## When to use - "Pick up where we left off" — session start on any long-running project - "Remember this" / "log that decision" the moment a choice lands - "What did we decide about <topic>, and why?" - "What does <codename/acronym> mean again?" — glossary lookups - "Wrap up" / "save state before we stop" — session end ## Workflow 1. Locate or initialize `memory/` at the project root: `decisions.md`, `context.md`, `glossary.md`, `sessions/`. Create missing files with headers; never overwrite existing ones. 2. Session start: read `context.md`, `decisions.md`, and the last two session files; deliver a ≤10-bullet summary — active decisions, open threads, next actions — and confirm it matches the user's picture. 3. During work, log decisions the moment they land: append to `decisions.md` with date, decision, rationale, and alternatives rejected. Same-session or it didn't happen. 4. New shorthand — nickname, acronym, codename — gets a one-line `glossary.md` entry on first use. 5. Session end: write `sessions/YYYY-MM-DD.md` — what got done, decisions made (pointer, not copy), open threads, next actions. 6. Monthly compaction: fold session files older than 30 days into `context.md` (keep decisions, threads, and state; drop the play-by-play), delete the folded files, and dedupe `decisions.md` keeping the latest ruling per top