Remember

Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history.

When to Use

• User wants to preserve knowledge discovered during a session
• Organizing scattered findings into structured memory
• Cleaning up duplicate or conflicting stored information

When NOT to Use

• Ephemeral task notes → just keep in conversation
• Already documented in code or docs → reference directly

Memory Surfaces

Workflow

1. Gather the relevant session findings
2. Classify each item:

• Durable project fact
• Temporary working note
• Operator preference or instruction
• Duplicate / stale / conflicting information

1. Propose the best destination for each item
2. Write or update only the appropriate memory surface
3. Call out duplicates or conflicts that should be cleaned up

Rules

• Do not dump everything into one store
• Prefer project memory for durable team knowledge
• Keep entries concise and actionable
• If something is uncertain, mark it as uncertain rather than storing it as fact

Output

• What was stored
• Where it was stored
• Any duplicates/conflicts found

Quality Gate (Before Storing)

Before committing anything to memory, apply this 3-question filter. Skip storage if the answer to any question is "No":

Examples

When to Update vs Create

• UPDATE an existing entry if the new information refines, corrects, or supersedes it
• CREATE a new entry only if no existing entry covers the topic
• DELETE entries that are provably outdated (check with user first)

See Also

• /coding-standards — canonical rules reference (no need to duplicate into memory)
• /skill-stocktake — audit memory surfaces for quality