claude-memory-bank-cli 1.0.0 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -4,6 +4,17 @@ This project uses an automatic persistent memory system. Claude MUST follow the
|
|
|
4
4
|
|
|
5
5
|
## Memory System Rules
|
|
6
6
|
|
|
7
|
+
### First Run (Empty Templates)
|
|
8
|
+
If memory bank files still contain placeholder text (like `[Project name will be auto-filled by Claude]`), this is a first run. You MUST:
|
|
9
|
+
1. Scan the entire project — read package.json, source files, folder structure, configs, README, etc.
|
|
10
|
+
2. Auto-populate ALL memory bank files with real information extracted from the codebase
|
|
11
|
+
3. Fill in `projectbrief.md` with the project's actual name, goals, and scope
|
|
12
|
+
4. Fill in `techContext.md` with the real tech stack, dependencies, and commands
|
|
13
|
+
5. Fill in `productContext.md` with what the project does and why
|
|
14
|
+
6. Fill in `patterns.md` with code conventions you detect in the existing code
|
|
15
|
+
7. Leave `activeContext.md`, `progress.md`, `decisions.md`, `troubleshooting.md` ready for use
|
|
16
|
+
8. Do this BEFORE responding to the user's first message
|
|
17
|
+
|
|
7
18
|
### On Every Conversation Start
|
|
8
19
|
1. Read ALL files in `memory-bank/` before doing anything else
|
|
9
20
|
2. Check `memory-bank/activeContext.md` to understand what was last being worked on
|
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
You MUST follow these rules automatically. No user command is needed.
|
|
4
4
|
|
|
5
|
+
## First Run Detection
|
|
6
|
+
- If memory bank files contain placeholder text (like `[Project name will be auto-filled by Claude]`), this is a fresh setup
|
|
7
|
+
- You MUST scan the entire codebase (package.json, source files, configs, README, folder structure) and auto-populate ALL memory bank files with real project information
|
|
8
|
+
- Do this BEFORE responding to the user's first message — the memory bank should never stay empty after a conversation
|
|
9
|
+
|
|
5
10
|
## At Conversation Start
|
|
6
11
|
- Read every file in `memory-bank/` and `memory-bank/extensions/` before responding to the user
|
|
7
12
|
- Use this context to understand the project state, what was worked on last, and what's pending
|