memory-bank

name	memory-bank
description	Scaffold and maintain a /memory_bank/ directory in any project. Provides human-readable context that survives tool changes and supplements user-cursor10x-mcp + user-devcontext session memory. Use when starting a new project, resuming after a long gap, or when the user asks to "set up memory" or "create a memory bank" for a project.

When to use

• Starting a new project that needs persistent human-readable context across sessions
• Resuming work on a project after a long gap with no session memory
• User asks to "set up memory" or "create a memory bank" for a project

On-demand loading: Read this skill only when the task clearly matches the description above or trigger phrases below. Do not load for unrelated work.

memory-bank

Purpose

Create or update a /memory_bank/ directory in the current project with five structured markdown files. These files persist project knowledge across tool changes, team members, and long pauses — complementing the session-based memory of user-cursor10x-mcp and user-devcontext.

---

When to activate

• User says: "set up memory bank", "init memory", "create project context files"
• Starting a new project with /project-init or /ks-conductor feature workflow
• Resuming work after > 1 week gap (prompt: "refresh memory from memory_bank/")
• memory_bank/ exists but some files are stale or missing

---

File structure to scaffold

Create these files under <project_root>/memory_bank/ if they do not exist (or update if explicitly requested):

memory_bank/
  projectbrief.md     ← high-level overview, goals, scope, constraints
  techContext.md      ← stack, versions, setup quirks, env var names
  systemPatterns.md   ← architecture patterns, coding standards, decisions
  activeContext.md    ← current work focus, recent changes (volatile — update often)
  progress.md         ← completed work, milestones, history

---

File templates

See references/file-templates.md for per-file markdown templates.

Integration with user-devcontext + user-cursor10x-mcp

These files are supplement, not replacement:

• user-devcontext: continue using initialize_conversation_context at session start
• user-cursor10x-mcp: continue using storeDecision, storeMilestone, recordEpisode
• memory_bank/: read manually when context is cold or switching tools

Recommended session start (when memory_bank/ exists):

1. Read activeContext.md and progress.md first (most volatile)
2. Read systemPatterns.md for architecture orientation
3. Then call getComprehensiveContext on user-cursor10x-mcp for recent episodes

---

Maintenance rules

• Update activeContext.md whenever the current focus changes
• Update progress.md when a milestone or decision is finalized
• Update techContext.md when dependencies, commands, or env vars change
• projectbrief.md and systemPatterns.md are stable — update only when scope or patterns genuinely change
• Keep each file under 300 lines; split or summarize when they grow