1  ---
 2  allowed-tools: Read, Grep, LS
 3  description: Quick audit of memory file coherence and boundaries
 4  ---
 5  
 6  # Memory Coherence Audit
 7  
 8  ## Context
 9  Perform a quick assessment of memory file coherence across the DreamNode memory pattern.
10  
11  ### Memory Files Analysis
12  - **User Memory**: @~/.claude/CLAUDE.md
13  - **Project Memory**: @CLAUDE.md  
14  - **Local Memory**: @CLAUDE.local.md
15  
16  ## Audit Checklist
17  
18  ### Boundary Violations
19  - [ ] Check for project-specific content in user memory
20  - [ ] Check for personal patterns in project memory  
21  - [ ] Check for non-local content in local memory
22  
23  ### Content Duplications
24  - [ ] Git commit philosophy mentioned in multiple files
25  - [ ] Memory management instructions repeated
26  - [ ] Development workflow duplicated
27  - [ ] Documentation patterns overlapping
28  
29  ### Outdated Information
30  - [ ] Repository migration content (already completed)
31  - [ ] Incorrect status information
32  - [ ] Wrong command counts or feature lists
33  - [ ] Conflicting roadmap information
34  
35  ### Structure Issues  
36  - [ ] Multiple "Current Status" sections
37  - [ ] Technical patterns in memory vs docs
38  - [ ] Missing cross-references to documentation
39  - [ ] Inconsistent terminology or naming
40  
41  ## Quick Fixes Needed
42  Based on audit findings, identify:
43  1. **Immediate boundary fixes**: What content needs to move between files
44  2. **Documentation extractions**: Technical content that should live in docs/
45  3. **Reference updates**: Links that need to point to correct locations
46  4. **Consistency improvements**: Naming, status, and terminology alignment
47  
48  ## Recommendation
49  If significant issues are found, run `/memory-coherence` for comprehensive cleanup.
50  If minor issues, proceed with targeted fixes using specific file edits.