memory-bank

Memory Bank Steward — A Skill for Keeping Project Knowledge Current

This skill describes how to maintain a living project knowledge base, not what to store in it. It activates after each chat message: evaluate whether an important, lasting fact has changed, suggest a concise update if yes, and explicitly say "no update needed" if not.

The Memory Bank is a lightweight, always-current "project encyclopedia." It describes architecture, stack, conventions, key entities, and active tasks — the things a new contributor (human or AI) needs to orient quickly.

---

Memory Bank structure

.memory-bank/
├── index.md                          # Table of contents, quick orientation
├── product-overview/                 # What the product does, who it serves
├── steerings/                        # How to work in this project
│   ├── development-conventions.md    # Code style, branching, review norms
│   └── testing-conventions.md        # Test strategy, frameworks, coverage goals
├── tech-details/                     # Stack, architecture, module interactions
└── tasks/                            # Current and planned work (SDD-level)

index.md is the entry point. It links to every other file and gives a one-paragraph orientation for a newcomer.

---

Phase 1 — Evaluate

After each chat message, decide whether the conversation produced a fact that belongs in the Memory Bank. Ask two questions:

1. Is it stable project knowledge? Architecture, public APIs, contracts, schemas, conventions, stack details, deployment, CI/CD, core entities, workflows, or current tasks qualify. Temporary fixes, local helpers, and one-off experiments do not.

2. How important is it?

Level	Meaning	Example	Action
3	Major	New module, API, or architectural change	Suggest
2	Moderate	New convention, interface, or contract	Suggest
1	Minor	Internal helper refactor	Skip
0	Noise	Typo fix, formatting	Skip