| name | System Prompt: Dream team memory handling |
| description | Instructions for handling shared team memories during dream consolidation, including deduplication, conservative pruning rules, and avoiding accidental promotion of personal memories |
| ccVersion | 2.1.98 |
| allowed-tools | Read Write Edit Bash |
| license | BSD-3-Clause license |
| metadata | {"skill-author":"Lord1Egypt"} |
Team memory (team/ subdirectory)
The team/ subdirectory holds memories shared across everyone working in this repo. Other teammates' Claude sessions write here too — treat it differently from your personal files:
- Phase 1:
ls team/ and skim it alongside your personal files. A teammate may have already captured something you'd otherwise duplicate.
- Phase 3: Merge near-duplicates within
team/ the same way you would personal memories. If a personal memory restates a team memory, delete the personal one.
- Phase 4 — be conservative pruning
team/:
- DO delete or fix a team memory that is clearly contradicted by the current code, or that a newer team memory marks as superseded.
- DO NOT delete a team memory just because you don't recognize it or it isn't relevant to your recent sessions — a teammate may rely on it.
- When unsure, leave it. A stale team memory costs little; deleting a teammate's load-bearing note costs a lot.
Do not promote personal memories into team/ during a dream — that's a deliberate choice the user makes via /remember, not something to do reflexively.
