memory-bank

Manage and persist project context across Claude Code sessions.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill memory-bank-parisgroup-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-bank
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/memory-bank
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill memory-bank-parisgroup-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains and updates a persistent memory store for Claude Code sessions, ensuring context survives restarts and handoffs.

Core Features & Use Cases

  • Structured memory bank: A defined project memory-bank with files like CLAUDE.md, memory-bank/projectbrief.md, etc., to capture context, decisions, and progress.
  • Session continuity: Reads memory-bank documents at session start and updates activeContext and progress as work evolves.
  • Knowledge preservation: Archives lessons, decisions, and changes to support seamless handoffs and future work.

Quick Start

Open CLAUDE.md and start populating memory-bank files to capture foundation, active context, and current priorities.

Frequently Asked Questions about memory-bank

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

FAQPage Schema
How do I preserve context across Claude Code sessions when restarting?

To preserve context across Claude Code sessions, use a memory-bank structure with a CLAUDE.md entry and a defined directory to read and write project context, ensuring continuity after restarts.

What is a memory bank and how does it maintain project documentation?

A memory bank is a structured directory containing files like CLAUDE.md, projectbrief.md, activeContext, and progress logs that capture project decisions, context, and progress for continuous session management.

When should I update the memory-bank files during a development workflow?

Update memory-bank files at session starts, feature completions, and architectural changes by writing to activeContext and progress logs to ensure project context remains current and accurate.

Can I use this memory-bank approach for project handoffs and knowledge preservation?

Yes, the memory-bank approach archives lessons, decisions, and changes to support seamless handoffs and future work by maintaining a persistent store of project context and historical logs.

What's the best way to start populating memory-bank files for a new project?

Open the CLAUDE.md file and begin populating memory-bank files to capture the foundation, active context, and current priorities, establishing the baseline structure for ongoing session management.