memory-manager

Stores git-ve rsioned, per-project memory in .claude/memory for teams to share context and decisions.

4|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JocDLC/saas-factory-v5 --skill memory-manager-jocdlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-manager
Source: https://github.com/JocDLC/saas-factory-v5/tree/main/.claude/skills/memory-manager
Command: npx skills add https://github.com/JocDLC/saas-factory-v5 --skill memory-manager-jocdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent per-project memory stored in the repository under .claude/memory, versioned with git and shareable with the team, replacing Claude Code's local auto-memory which doesn't travel with the project. It ensures contextual knowledge survives across sessions and teammates, and can be loaded proactively at the start of work to improve consistency.

Core Features & Use Cases

  • Per-project, git-versioned memory stored inside the repo for teams to share context and decisions.
  • Memory is organized under .claude/memory with subfolders for user, feedback, project, and reference to structure knowledge.
  • Clear activation workflow: initialize folders, create MEMORY.md, and instruct users when to recall or save information.

Quick Start

Follow the activation guide to disable Claude Code auto-memory, create the .claude/memory folders, and initialize MEMORY.md.

Frequently Asked Questions about memory-manager

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

FAQPage Schema
How do I share Claude Code project memory with my team across different sessions?

You can share Claude Code project memory by storing it under .claude/memory in your repository. This approach versions context with git, allowing teammates to access shared decisions and bugs.

How do I set up per-project memory that travels with my codebase?

To set up per-project memory, follow the activation workflow to disable Claude Code auto-memory, create the .claude/memory folders, and initialize MEMORY.md to start storing repository context.

What is git-versioned memory and how does it work for software development teams?

Git-versioned memory stores shared context, decisions, and bugs inside the repository under .claude/memory. It ensures persistent knowledge survives across sessions and collaborators by tracking changes with git.

Does Claude Code local auto-memory travel with the repository when switching machines?

Claude Code local auto-memory does not travel with the repository. You need per-project memory stored under .claude/memory to ensure contextual knowledge is versioned and shared with your team.

Can I organize shared project context into different categories within the repository?

You can organize shared project context under .claude/memory using subfolders for user, feedback, project, and reference. This structure helps categorize knowledge for the entire team.

When should I not use local auto-memory for collaborative software development?

You should not use local auto-memory for collaborative development because it does not travel with the repository. Per-project git-versioned memory is required to share context across sessions and teammates.