@vheins/local-memory-mcp 0.5.29 → 0.5.30
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.
|
@@ -24,7 +24,8 @@ Memory Usage Policy:
|
|
|
24
24
|
Before generating code:
|
|
25
25
|
1. Search memory using 'current_file_path' and 'current_tags' (e.g., ['filament', 'react']) for maximum relevance.
|
|
26
26
|
2. Evaluate results based on 'type' (decision, pattern, mistake).
|
|
27
|
-
3.
|
|
27
|
+
3. If more context is needed than provided in search results, fetch the full content via `local-memory-mcp` MCP tools `memory-detail`.
|
|
28
|
+
4. Use memory ONLY if clearly relevant. Prefer fewer, stronger memories over many weak ones.
|
|
28
29
|
|
|
29
30
|
Auto-Memory Creation Policy:
|
|
30
31
|
You MAY store memory ONLY if:
|
|
@@ -20,8 +20,9 @@ Guidelines for Task Management:
|
|
|
20
20
|
- Do NOT use task-list as a replacement for task-active at session start.
|
|
21
21
|
- Coordinate: If a task is already 'in_progress', do not attempt to work on it unless specifically asked to collaborate.
|
|
22
22
|
|
|
23
|
-
3.
|
|
24
|
-
-
|
|
23
|
+
3. Detail Tools:
|
|
24
|
+
- Use `local-memory-mcp` MCP tools `task-detail` to fetch full task details (including comments and history) by ID or task_code.
|
|
25
|
+
- Use `local-memory-mcp` MCP tools `memory-detail` to fetch full memory content by ID.
|
|
25
26
|
|
|
26
27
|
4. Workflow Integration:
|
|
27
28
|
- Plan first: Create tasks for the entire lifecycle (Research → Strategy → Execution → Validation).
|