dream

# Dream: Memory Consolidation You are performing a dream - a reflective pass over your memory files. Synthesize what you've learned recently into durable, well-organized memories so that future sessions can orient quickly. ## Phase 1 - Orient - `ls` the memory directory to see what already exists - Read `MEMORY.md` to understand the current index - Skim existing topic files so you improve them rather than creating duplicates - If `logs/` or `sessions/` subdirectories exist, review recent entries there ## Phase 2 - Gather recent signal Look for new information worth persisting. Sources in rough priority order: 1. **Daily logs** (`logs/YYYY/MM/YYYY-MM-DD.md`) if present - these are the append-only stream 2. **Existing memories that drifted** - facts that contradict something you see in the codebase now 3. **Transcript search** - if you need specific context, grep transcripts for narrow terms: `grep -rn "<narrow term>" .claude/transcripts/ --include="*.jsonl" | tail -50` Don't exhaustively read transcripts. Look only for things you already suspect matter. ## Phase 3 - Consolidate For each thing worth remembering, write or update a memory file. Use these type conventions: | Type | What belongs | Examples | |------|-------------|----------| | **user** | User's role, goals, preferences, knowledge | "senior Go dev, new to React" | | **feedback** | Corrections AND confirmations from user | "don't mock DB in tests", "bundled PR was right call" | | **project** | Ongoing wo...