Session Memory Skill

Manage the Asciicker session memory system: load recent context, create summaries, compress old sessions, and search memory.

Commands

Load Recent Context

Trigger: "load recent work", "what did we work on recently", "show recent sessions"

Action:

•Read .claude/memory/recent/INDEX.md
•Read the 1-3 most recent session files
•Read current week's compressed summary (if exists)
•Summarize recent activity and current status

Example:

code

User: "Load my recent work"
Claude: *Reads recent INDEX and sessions*
        "Recent activity: MCP server reorganization (completed),
        session memory system (in progress).
        Current focus: Phase 2 implementation."

Summarize Current Session

Trigger: "summarize this session", "what have we done today", "session summary"

Action:

•Review conversation history
•Extract key activities, decisions, and changes
•Generate summary in session file format
•Offer to create/update session file

Example:

code

User: "Summarize this session"
Claude: *Analyzes conversation*
        "Created 5 template files, updated rules.md,
        implemented session memory system Phase 1.
        Ready to create session file?"

Compress Old Sessions

Trigger: "compress old sessions", "create weekly summary", "archive sessions"

Action:

•Find sessions >7 days old in recent/
•Group by week (Monday-Sunday)
•Extract key information using weekly template
•Create compressed/YYYY-MM-weekNN.md
•Optionally delete old session files

Example:

code

User: "Compress old sessions"
Claude: *Searches recent/*
        "Found 8 sessions from week 50 (Dec 16-22).
        Creating weekly summary..."

Search Memory

Trigger: "search memory for X", "what did we decide about Y", "find session about Z"

Action:

•Use Grep to search memory/**/*.md for query
•Show matching sessions and summaries
•Provide context links

Example:

code

User: "What did we decide about Python versions?"
Claude: *Greps memory/*
        "Found in session-2025-12-28-reorg:
        Decision: Use Python 3.11 for Serena MCP
        (requires >=3.11, <3.12)"

Integration

With Context System

•Sessions link to context docs
•Discoveries migrate to context/
•Memory provides just-in-time context

With Skills

•Other skills can invoke memory loading
•Memory informs skill behavior
•Cross-skill context sharing

Usage Examples

Start of New Session

code

User: "Continue work on multi-tile brush"
Skill: *Loads recent sessions tagged 'terrain'*
       "Last session: Implemented brush size controls.
       Issue: Patch boundary calculation needs fix.
       Files: asciiid.cpp lines 5100-5150"

Mid-Session Check

code

User: "What have we accomplished today?"
Skill: *Summarizes current session*
       "Today: Fixed Python venv (3.11),
       reorganized MCP servers,
       created session memory system"

Weekly Review

code

User: "Compress last week's sessions"
Skill: *Creates weekly summary*
       "Compressed 7 sessions from week 51.
       Major: MCP reorganization complete,
       memory system implemented"

Research Question

code

User: "Have we worked on terrain height before?"
Skill: *Searches memory*
       "Yes, 3 sessions:
       - 2025-12-26: Terrain height fix (0xA000)
       - 2025-12-24: Water level issue
       - 2025-12-23: Material visibility problem"

File Locations

•Recent Sessions: ../../memory/recent/
•Compressed History: ../../memory/compressed/
•Templates: Use session-template.md and weekly-template.md
•Documentation: ../../memory/README.md

Best Practices

•Start sessions intentionally: Create session file at start of work
•Update incrementally: Don't wait until end to write everything
•Be selective: Remember decisions, not every file read
•Link context: Connect memory to permanent docs
•Compress regularly: Weekly summaries prevent overwhelming recent/

This skill helps maintain session continuity across days/weeks while keeping memory organized and searchable.