remember

name	remember
description	Use at the end of a work session, before /clear, or when the context window is filling — when the next session would otherwise start cold and re-explain decisions already made. Also use the moment a durable decision or convention gets established mid-session.

remember

Overview

Every new session starts at zero unless you carry state forward. remember compresses a session into a durable memory file the next session loads on open — continuity without re-explaining yesterday.

When to use

• Wrapping up a session → remember save.
• A decision, pattern, or convention was just established and must survive the session.
• Context is filling and you're about to compact or /clear.
• Starting fresh and you want prior state → remember restore.

Process — save

1. Compress the session into four buckets: decisions made, patterns/conventions established, progress completed, open threads + next step.
2. Write to the project memory file (e.g. context/memory.md or progress-tracker.md) — update in place, don't append endlessly. Keep it scannable.
3. Convert relative dates to absolute. Drop anything the code already records.

Process — restore

1. Read the memory file first thing, before any work.
2. Re-anchor in one line: the goal, what's done, the next step. Then proceed.

What to capture (and not)

Capture: choices + the why, conventions, where things stand, the next action. Skip: anything obvious from the code, full transcripts, one-off chatter.

Common mistakes

• Saving a transcript instead of a compression → unreadable and expensive. Compress.
• Recording what the code does → the code already says that. Record decisions and why.
• Never restoring → the memory file is dead weight if the next session doesn't read it first.