Update memory instruction

Author: codeaholicguy

.ai-devkit.json

@@ -1,7 +1,8 @@
 {
   "version": "0.4.2",
   "environments": [
-    "antigravity"
+    "cursor",
+    "claude"
   ],
   "initializedPhases": [
     "requirements",
@@ -11,5 +12,5 @@
     "testing"
   ],
   "createdAt": "2025-12-28T13:35:45.251Z",
-  "updatedAt": "2026-01-15T18:27:24.093Z"
+  "updatedAt": "2026-01-25T14:05:14.517Z"
 }

.claude/commands/capture-knowledge.md

@@ -1,12 +1,11 @@
+---
+description: Capture structured knowledge about a code entry point and save it to the knowledge docs.
+---
+
 # Knowledge Capture Assistant
 
 Guide me through creating a structured understanding of a code entry point and saving it to the knowledge docs.
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
-
 ## Step 1: Gather Context
 - Entry point (file, folder, function, API)
 - Why this entry point matters (feature, bug, investigation)

.claude/commands/check-implementation.md

@@ -1,9 +1,8 @@
-Compare the current implementation with the design in docs/ai/design/ and requirements in docs/ai/requirements/. Please follow this structured review:
+---
+description: Compare implementation with design and requirements docs to ensure alignment.
+---
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
+Compare the current implementation with the design in docs/ai/design/ and requirements in docs/ai/requirements/. Please follow this structured review:
 
 1. Ask me for:
    - Feature/branch description

.claude/commands/code-review.md

@@ -1,12 +1,11 @@
+---
+description: Perform a local code review before pushing changes, ensuring alignment with design docs and best practices.
+---
+
 # Local Code Review Assistant
 
 You are helping me perform a local code review **before** I push changes. Please follow this structured workflow.
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
-
 ## Step 1: Gather Context
 Ask me for:
 - Brief feature/branch description

.claude/commands/debug.md

@@ -1,12 +1,11 @@
+---
+description: Guide me through debugging a code issue by clarifying expectations, identifying gaps, and agreeing on a fix plan before changing code.
+---
+
 # Local Debugging Assistant
 
 Help me debug an issue by clarifying expectations, identifying gaps, and agreeing on a fix plan before changing code.
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
-
 ## Step 1: Gather Context
 Ask me for:
 - Brief issue description (what is happening?)

.claude/commands/execute-plan.md

@@ -1,12 +1,11 @@
+---
+description: Execute a feature plan interactively, guiding me through each task while referencing relevant docs and updating status.
+---
+
 # Feature Plan Execution Assistant
 
 Help me work through a feature plan one task at a time.
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
-
 ## Step 1: Gather Context
 Ask me for:
 - Feature name (kebab-case, e.g., `user-authentication`)

.claude/commands/new-requirement.md

@@ -1,9 +1,8 @@
-I want to add a new feature/requirement. Please guide me through the complete development workflow:
+---
+description: Add new feature/requirement documentation and guide me through the development workflow from requirements to testing.
+---
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
+I want to add a new feature/requirement. Please guide me through the complete development workflow:
 
 ## Step 1: Capture Requirement
 First, ask me:

.claude/commands/remember.md

@@ -1,3 +1,9 @@
+---
+description: Store reusable guidance in the knowledge memory service.
+---
+
+# Remember Knowledge
+
 When I say "remember this" or want to save a reusable rule, help me store it in the knowledge memory service.
 
 ## Step 1: Capture Knowledge
@@ -15,8 +21,7 @@ If I'm vague, ask follow-ups to make it specific and actionable.
 
 ## Step 3: Store
 Call `memory.storeKnowledge` with title, content, tags, scope.
-If MCP tools are unavailable, use `ai-devkit memory store` instead.
+If MCP tools are unavailable, use `npx ai-devkit memory store` instead.
 
 ## Step 4: Confirm
-Summarize what was saved and offer to store more knowledge if needed.
-
+Summarize what was saved and offer to store more knowledge if needed.

.claude/commands/review-design.md

@@ -1,9 +1,8 @@
-Review the design documentation in docs/ai/design/feature-{name}.md (and the project-level README if relevant). Summarize:
+---
+description: Review the design documentation for a feature to ensure completeness and accuracy.
+---
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
+Review the design documentation in docs/ai/design/feature-{name}.md (and the project-level README if relevant). Summarize:
 
 - Architecture overview (ensure mermaid diagram is present and accurate)
 - Key components and their responsibilities

.claude/commands/review-requirements.md

@@ -1,9 +1,8 @@
-Please review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment. Summarize:
+---
+description: Review the requirements documentation for a feature to ensure completeness and alignment with project standards.
+---
 
-## Memory (use when helpful)
-- If you need clarification or project conventions, query `memory.searchKnowledge` with a brief task description, tags, and scope.
-- If I ask to save reusable guidance, run `/remember` (or call `memory.storeKnowledge`).
-- If MCP tools are unavailable, use `ai-devkit memory search` or `ai-devkit memory store`.
+Please review `docs/ai/requirements/feature-{name}.md` and the project-level template `docs/ai/requirements/README.md` to ensure structure and content alignment. Summarize:
 
 - Core problem statement and affected users
 - Goals, non-goals, and success criteria