session-context

vieko's avatarfrom vieko

Read project session context from .sessions/index.md to understand ongoing work, previous decisions, blockers, and history. Use when the user asks about project context, previous sessions, what was worked on before, architectural decisions, blockers, or when they reference "last time", "previously", "the session", or "what we decided".

⭐3stars🔀0forks📁View on GitHub🕐Updated Dec 22, 2025

When & Why to Use This Skill

The session-context Claude skill provides a structured mechanism for AI agents to maintain long-term project continuity. By reading from a dedicated .sessions directory, it enables the agent to retrieve historical context, previous architectural decisions, and ongoing blockers, ensuring seamless transitions between development sessions without relying on limited conversation memory.

Use Cases

  • Resuming Development: Quickly catch up on project progress and 'last session' activities to maintain workflow continuity when starting a new interaction.
  • Decision Retrieval: Access the rationale behind past architectural choices and technical decisions to ensure new code remains consistent with the project's history.
  • Blocker Identification: Review pending issues, known bugs, or documented blockers from previous sessions before initiating new implementation tasks.
  • Project Status Overview: Provide a comprehensive summary of the current project state, active plans, and recent work history for better situational awareness.
namesession-context
descriptionRead project session context from .sessions/index.md to understand ongoing work, previous decisions, blockers, and history. Use when the user asks about project context, previous sessions, what was worked on before, architectural decisions, blockers, or when they reference "last time", "previously", "the session", or "what we decided".
allowed-toolsRead, Glob

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

  1. Read .sessions/index.md to understand:

    • Current project status and recent work
    • Active decisions and their rationale
    • Known blockers or pending issues
    • Links to relevant plans or documentation
  2. Check .sessions/plans/ if the user asks about implementation plans

  3. Check .sessions/docs/ if the user asks about documented topics

  4. For monorepos, check .sessions/packages/ for package-specific context

File Structure

.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-session slash command
  • Don't modify .sessions/index.md unless explicitly asked