skills.rest
JKHeadley
JKHeadleyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

agent-memory

Persist project knowledge across Claude Code sessions using MEMORY.md.

75|18|Updated Feb 19, 2026
Search Tags:#claude code#memory#session continuity#persistent state#project notes#context compaction
One-click install
npx skills add https://github.com/JKHeadley/instar --skill agent-memory-jkheadley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-memory
Source: https://github.com/JKHeadley/instar/tree/main/skills/agent-memory
Command: npx skills add https://github.com/JKHeadley/instar --skill agent-memory-jkheadley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of lost context in Claude Code by giving the agent a durable place to store project knowledge, lessons learned, and user preferences across sessions.

Core Features & Use Cases

  • Persistent Memory File: Uses a single MEMORY.md file as the agent's long-term notebook for project-specific knowledge.
  • Topic-Based Organization: Splits growing memory into focused topic files when notes become too large to manage cleanly.
  • Maintenance Guidance: Explains what to record, what to omit, when to prune stale notes, and how to keep memory useful over time.
  • Use Case: A developer can preserve hard-won debugging fixes, recurring commands, and communication preferences so the next Claude Code session starts informed instead of blank.

Quick Start

Create .claude/MEMORY.md, tell Claude Code to read it at the start of every session, and keep adding important project discoveries as you learn them.

Frequently Asked Questions about agent-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep Claude Code memory between sessions?▼

To keep Claude Code memory between sessions, create a single MEMORY.md file to store project knowledge, debugging lessons, and preferences, then instruct Claude Code to read it at the start of each session.

How does persistent state work after context compaction?▼

Persistent state after context compaction requires explicit read and write guidance to save evolving topic notes into your MEMORY.md file, ensuring project context is retained and not lost.

What is the best way to organize project notes for Claude Code?▼

The best way to organize project notes for Claude Code is using a single MEMORY.md file initially, then splitting growing memory into focused topic files when notes become too large to manage cleanly.

Can I use a memory file to store debugging lessons and recurring commands?▼

Yes, you can use a memory file to store hard-won debugging fixes, recurring commands, and communication preferences so your next Claude Code session starts fully informed.

When should I prune stale notes from my agent's persistent memory?▼

You should prune stale notes from your agent's persistent memory when the project notes become too large to manage cleanly or when previous debugging lessons no longer apply to the current workflow.

Does Claude Code require a specific file format for session continuity?▼

Claude Code requires a single MEMORY.md file for session continuity, along with optional topic files to organize expanding project knowledge, preferences, and commands over time.

Related Skills

Explore More Software Engineering Skills→
c-dalyc-daly

distill

Distill episodic session learnings from EPISODES.md into persistent memory patterns in MEMORY.md.

Community
Intermediate
JKHeadleyJKHeadley
75

agent-identity

Create persistent agent identity files for Claude Code sessions.

Community
Intermediate
radenadriradenadri

persistent-memory

Store session history, decisions, and handoffs in portable file-based memory.

Community
Advanced
koasis89koasis89

note

Create and manage notes using OMX persistent memory features.

Community
Basic