Session Context
This project uses the Sessions Directory Pattern to maintain continuity across AI coding sessions. Context is stored in .sessions/index.md rather than relying on conversation memory.
When to Use This Skill
Read session context when the user:
- •Asks about previous work or decisions
- •References "last time", "previously", "before"
- •Wants to know about blockers or pending issues
- •Asks what the project status is
- •Starts a significant task that might have prior context
Instructions
- •
Read
.sessions/index.mdto understand:- •Current project status and recent work
- •Active decisions and their rationale
- •Known blockers or pending issues
- •Links to relevant plans or documentation
- •
Check
.sessions/plans/if the user asks about implementation plans - •
Check
.sessions/docs/if the user asks about documented topics - •
For monorepos, check
.sessions/packages/for package-specific context
File Structure
code
.sessions/ ├── index.md # Main session context (read this first) ├── archive/ # Completed work history ├── docs/ # Topic documentation ├── plans/ # Implementation plans ├── prep/ # Pre-session context └── packages/ # Monorepo package notes (if applicable)
Important
- •This skill is for reading context, not updating it
- •Session updates happen via
/end-sessionslash command - •Don't modify
.sessions/index.mdunless explicitly asked