Session Memory
Overview
Persistent memory system that survives Claude Code's message compaction. Uses three markdown files in .claude/cc10x/ as a permission-free database for continuity, consistency, and pattern compounding.
Memory Surfaces
- activeContext.md -- Current focus, decisions, learnings, next steps, blockers
- patterns.md -- Project conventions, architecture decisions, common gotchas, reusable solutions
- progress.md -- Task completion tracking with verification evidence
Iron Law
EVERY WORKFLOW MUST:
- LOAD memory at START (and before key decisions)
- UPDATE memory at END (and after learnings/decisions)
Stable Edit Anchors
Safe section headers for Edit operations:
- activeContext:
## Recent Changes,## Learnings,## References - patterns:
## Common Gotchas,## Project SKILL_HINTS - progress:
## Completed,## Verification
Read-Edit-Verify Pattern
- Read file
- Verify anchor exists
- Edit with exact
old_string - Read back to confirm
Tool Rules
- Use
Write()for NEW files (permission-free) - Use
Edit()for EXISTING files (permission-free) - Never use
Write()to overwrite existing files - Never compound commands (
mkdir && cat)
When to Use
- At the start of every CC10X workflow (load)
- At the end of every CC10X workflow (update)
- Before making key decisions (check patterns)
- After discovering learnings or gotchas (persist)
Agents Used
All CC10X agents use this skill. The cc10x-router manages load/update lifecycle.