Session Continuity
Resume exactly where you left off. The Session Loop pattern ensures context persists across sessions and AI-to-AI handoffs.
3 files. 8 commands. Zero scripts. Built for Claude Code.
# Clone and copy to your project
git clone --depth 1 https://github.com/rexkirshner/ai-context-system.git
mkdir -p /path/to/your/project/.claude
cp -r ai-context-system/.claude/commands /path/to/your/project/.claude/
cp ai-context-system/.claude/VERSION /path/to/your/project/.claude/
rm -rf ai-context-system
# In Claude Code, initialize
/init-contextThis creates CLAUDE.md, context/STATUS.md, and context/DECISIONS.md.
your-project/
├── CLAUDE.md # Entry point (auto-loaded by Claude Code)
├── .claude/
│ ├── VERSION # Installed version (6.0.2)
│ └── commands/ # 8 slash commands
└── context/
├── STATUS.md # Current state + Working Set
└── DECISIONS.md # Decision log (why)Every session follows this pattern:
context/STATUS.md/saveThat's it. No complex workflows. No validation machinery.
| Command | Purpose |
|---|---|
/init-context | Create context files (never overwrites) |
/save | Update STATUS.md, record decisions autonomously |
/update-context-system | Update commands (v6.x only) |
/review-security | Security audit (report only) |
/review-performance | Performance review (report only) |
/review-accessibility | Accessibility review (report only) |
/review-seo | SEO review (report only) |
/review-cost | Cost optimization review (report only) |
v6.0.2 — Migration Improvements
migrate-to-v6.sh script, v6.x uses /update-context-system/save detects v5.x format and stops instead of corrupting filesThe value is in the subtraction.
v5.x had 22 commands, 14 agents, and 150KB of shell scripts. It was overengineered.
v6.0 asks: what's the minimum needed for session continuity? Three files and a simple loop.