memory-banklisted

Maintain and update project memory-bank files for persistent context across Claude Code sessions. Use when starting a new session, completing features, making architectural changes, or when context needs to be preserved. Triggers on: memory bank, project context, session start, context update, CLAUDE.md, project status, handoff, continue work.
parisgroup-ai/imersao-ia-setup · ★ 1 · Data & Documents · score 80

Install: claude install-skill parisgroup-ai/imersao-ia-setup

# Memory Bank Skill This skill manages the project's memory-bank system - a structured set of files that preserve context between Claude Code sessions. The memory-bank ensures continuity, reduces repetitive explanations, and maintains project intelligence. ## Core Philosophy Claude's memory resets between sessions. The memory-bank serves as persistent project memory: 1. **Read** memory-bank files at session start 2. **Use** context throughout the session 3. **Update** files before session ends or after significant changes ## Memory Bank Structure ``` project-root/ ├── CLAUDE.md # Primary entry point (required) ├── memory-bank/ │ ├── projectbrief.md # Foundation document │ ├── productContext.md # Why and how │ ├── activeContext.md # Current focus (update frequently) │ ├── systemPatterns.md # Architecture patterns │ ├── techContext.md # Technical details │ ├── progress.md # What's done, what's next (keep slim!) │ ├── errors.md # Known issues and solutions │ └── archive/ # (Optional) Historical details │ ├── index.md # Quick lookup for archived items │ └── YYYY-MM.md # Monthly archives (e.g., 2025-12.md) ``` ### When to Archive When `progress.md` exceeds ~500 lines, split it: 1. **Keep in progress.md**: Current sprint, next up, milestone summary table, known issues 2. **Move to archive/**: Detailed session logs, files