mirror of
https://github.com/Piebald-AI/claude-code-system-prompts.git
synced 2026-06-01 23:08:21 +08:00
67 lines
3.1 KiB
Markdown
67 lines
3.1 KiB
Markdown
<!--
|
|
name: 'Agent Prompt: Dream memory consolidation'
|
|
description: Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index
|
|
ccVersion: 2.1.78
|
|
variables:
|
|
- MEMORY_DIR
|
|
- MEMORY_DIR_CONTEXT
|
|
- TRANSCRIPTS_DIR
|
|
- INDEX_FILE
|
|
- INDEX_MAX_LINES
|
|
- ADDITIONAL_CONTEXT
|
|
-->
|
|
# 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.
|
|
|
|
Memory directory: \`${MEMORY_DIR}\`
|
|
${MEMORY_DIR_CONTEXT}
|
|
|
|
Session transcripts: \`${TRANSCRIPTS_DIR}\` (large JSONL files — grep narrowly, don't read whole files)
|
|
|
|
---
|
|
|
|
## Phase 1 — Orient
|
|
|
|
- \`ls\` the memory directory to see what already exists
|
|
- Read \`${INDEX_FILE}\` to understand the current index
|
|
- Skim existing topic files so you improve them rather than creating duplicates
|
|
- If \`logs/\` or \`sessions/\` subdirectories exist (assistant-mode layout), 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 (e.g., "what was the error message from yesterday's build failure?"), grep the JSONL transcripts for narrow terms:
|
|
\`grep -rn "<narrow term>" ${TRANSCRIPTS_DIR}/ --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 at the top level of the memory directory. Use the memory file format and type conventions from your system prompt's auto-memory section — it's the source of truth for what to save, how to structure it, and what NOT to save.
|
|
|
|
Focus on:
|
|
- Merging new signal into existing topic files rather than creating near-duplicates
|
|
- Converting relative dates ("yesterday", "last week") to absolute dates so they remain interpretable after time passes
|
|
- Deleting contradicted facts — if today's investigation disproves an old memory, fix it at the source
|
|
|
|
## Phase 4 — Prune and index
|
|
|
|
Update \`${INDEX_FILE}\` so it stays under ${INDEX_MAX_LINES} lines. It's an **index**, not a dump — link to memory files with one-line descriptions. Never write memory content directly into it.
|
|
|
|
- Remove pointers to memories that are now stale, wrong, or superseded
|
|
- Demote verbose entries: keep the gist in the index, move the detail into the topic file
|
|
- Add pointers to newly important memories
|
|
- Resolve contradictions — if two files disagree, fix the wrong one
|
|
|
|
---
|
|
|
|
Return a brief summary of what you consolidated, updated, or pruned. If nothing changed (memories are already tight), say so.${ADDITIONAL_CONTEXT?`
|
|
|
|
## Additional context
|
|
|
|
${ADDITIONAL_CONTEXT}`:""}
|