Create a persistent project memory bank under memory-bank/ (kebab-case filenames), including an imports area for reference material.
Rules:
Do NOT overwrite existing files.
Do NOT delete or rename any existing files.
If a directory or file already exists, leave it unchanged.
If a required file is missing, create it using the templates below.
After completion, print a short summary listing what was created vs what already existed.
Steps:
Ensure the memory-bank/ directory exists at the workspace root.
Ensure the memory-bank/imports/ directory exists at the workspace root.
Ensure the following memory-bank/imports/ subdirectories exist:
memory-bank/imports/api/
memory-bank/imports/schemas/
memory-bank/imports/diagrams/
memory-bank/imports/references/
Ensure the following memory-bank/ files exist:
memory-bank/README.md
memory-bank/index.md
関連 Skill
memory-bank/project-brief.md
memory-bank/product-context.md
memory-bank/active-context.md
memory-bank/system-patterns.md
memory-bank/tech-context.md
memory-bank/progress.md
memory-bank/conventions.md
memory-bank/decisions.md
memory-bank/glossary.md
Ensure the following imports README exists:
memory-bank/imports/README.md
Templates (use these exactly for newly created files):
========================
memory-bank/README.md
Project Memory (memory-bank/)
This directory contains persistent project context shared by humans and automated tools.
It is the source of truth for understanding why this project exists, how it is built,
and what is currently happening.
If you are new to this repository, start here.
Why This Exists
Projects accumulate context faster than code:
architectural decisions
constraints and tradeoffs
ongoing work
“gotchas” that aren’t obvious from reading files
The memory-bank/ directory captures that context in a structured, version-controlled way so it:
doesn’t live only in people’s heads
doesn’t get lost across sessions
stays close to the code
How to Use This Folder
If you are a developer:
Read these files before making significant changes
Update them when your work changes project direction or status
Treat them like living documentation, not static specs
If you are reviewing a PR:
Check whether relevant memory-bank/ files were updated
Especially:
active-context.md
progress.md
decisions.md
If you are onboarding:
Read project-brief.md
Read system-patterns.md
Skim tech-context.md
Check active-context.md to see what’s happening now
This folder contains supporting reference material that helps developers and automated tools understand
the project, but is not part of the core memory files.
Examples:
API specifications (OpenAPI/Swagger, Postman collections)
Database schemas or ERDs
Architecture diagrams
External vendor docs or integration notes
Request/response examples
“Golden” JSON payloads used for tests
Where to Put Things
api/ — OpenAPI specs, Postman collections, API examples