/remember — Store to Memory

Three-Tier Memory Architecture

Tier	Location	Loaded	Purpose
1	.claude/memory/index.md	Always	One-line pointers — tiny, fast
2	.claude/memory/topics/*.md	On demand	Detailed topic files
3	Session transcripts	Never whole	Raw history, searchable via grep

How to Store

Step 1: Write the topic file

Create .claude/memory/topics/<slug>.md:

# <Topic Title>

Last verified: YYYY-MM-DD

<Content: decisions, patterns, context, rationale>

Keep it scannable. Use bullet points. Include why, not just what.

Step 2: Add pointer to index

Append one line to .claude/memory/index.md:

- [<Topic Title>](topics/<slug>.md) — <one-line hook, under 120 chars>

Rules

• Check if a related topic already exists before creating a new one — update instead
• Include Last verified: date so future sessions know staleness
• Don't store things derivable from code or git history
• Don't store ephemeral task details — those belong in tasks, not memory
• Frame stored knowledge as "Previously noted (may be outdated)" when recalled
• Max 50 lines per topic file. If it's longer, split into subtopics.

What to Store

Good candidates:

• Architectural decisions and their rationale
• User preferences that affect how you work
• Non-obvious project constraints (deadlines, compliance requirements)
• Patterns that took multiple attempts to discover
• External resource locations (dashboards, issue trackers, docs)

Bad candidates:

• Code structure (read the code)
• Git history (use git log)
• Current task progress (use tasks)
• Debugging solutions (the fix is in the code)