feat(skill): update memory instruction

Author: codeaholicguy

skills/agent-orchestration/SKILL.md

@@ -118,4 +118,4 @@ Then go back to step 1.
 
 ## Completion
 
-When all agents are idle with no remaining work, give the user a final summary: what each agent accomplished, issues encountered, and overall outcome. Store significant coordination issues or patterns via the `memory` skill with tags `orchestration,lesson-learned`. Then stop.
+When all agents are idle with no remaining work, give the user a final summary: what each agent accomplished, issues encountered, and overall outcome. Store significant coordination issues: `npx ai-devkit@latest memory store --title "<issue>" --content "<details>" --tags "orchestration,lesson-learned"`. Then stop.

skills/capture-knowledge/SKILL.md

@@ -15,7 +15,7 @@ Build structured understanding of code entry points with an analysis-first workf
 1. Gather & Validate
 - Confirm entry point (file, folder, function, API), purpose, and desired depth.
 - Verify it exists; resolve ambiguity or suggest alternatives if not found.
-- Search the `memory` skill for existing knowledge about this entry point before analyzing.
+- Search for existing knowledge before analyzing: `npx ai-devkit@latest memory search --query "<entry point name or purpose>"`
 
 2. Collect Source Context
 - Summarize purpose, exports, key patterns.

skills/debug/SKILL.md

@@ -15,7 +15,7 @@ Debug with an evidence-first workflow before changing code.
 1. Clarify
 - Restate observed vs expected behavior in one concise diff.
 - Confirm scope and measurable success criteria.
-- Search the `memory` skill for similar past incidents before investigating.
+- Before investigating, search for similar past incidents: `npx ai-devkit@latest memory search --query "<observed behavior>" --tags "debug,root-cause"`
 
 2. Reproduce
 - Capture minimal reproduction steps.
@@ -36,7 +36,7 @@ For each hypothesis, include:
 - Confirm a pre-fix failing signal exists.
 - Confirm post-fix success using the `verify` skill — including regression verification for bug fixes.
 - Summarize remaining risks and follow-ups.
-- Store the root cause and fix via the `memory` skill with tags `debug,root-cause` so future sessions can skip repeated investigation.
+- Store root cause and fix for future sessions: `npx ai-devkit@latest memory store --title "<root cause>" --content "<diagnosis and fix>" --tags "debug,root-cause"`
 
 ## Red Flags and Rationalizations
 

skills/dev-lifecycle/SKILL.md

@@ -70,10 +70,10 @@ Phases: `requirements/`, `design/`, `planning/`, `implementation/`, `testing/`.
 
 ## Memory Integration
 
-Use the `memory` skill in any phase that involves clarification questions (typically Phases 1-3):
+In phases with clarification questions (typically 1-3), run these CLI commands (see the `memory` skill for full options):
 
-1. **Before asking questions**: search for existing knowledge. Apply matches; only ask about uncovered gaps.
-2. **After clarification**: store new knowledge for future sessions.
+1. **Before asking** — search first, only ask about uncovered gaps: `npx ai-devkit@latest memory search --query "<topic>"`
+2. **After clarification** — store for future sessions: `npx ai-devkit@latest memory store --title "<title>" --content "<insight>" --tags "<tags>"`
 
 ## Red Flags and Rationalizations
 

skills/simplify-implementation/SKILL.md

@@ -15,7 +15,7 @@ Reduce complexity with an analysis-first approach before changing code.
 
 1. Gather Context
 - Confirm targets, pain points, and constraints (compatibility, API stability, deadlines).
-- Search the `memory` skill for past simplification decisions or known constraints in this area.
+- Search for past simplification decisions or known constraints: `npx ai-devkit@latest memory search --query "<target area>" --tags "simplify"`
 
 2. Analyze Complexity
 - Identify sources (nesting, duplication, coupling, over-engineering, magic values).

skills/tdd/SKILL.md

@@ -63,4 +63,4 @@ Then pick the next behavior and repeat.
 
 ## Memory Integration
 
-After completing a TDD session, store reusable test patterns via the `memory` skill — e.g., test setup for a specific framework, common assertion patterns, or fixtures that were hard to get right.
+After completing a TDD session, store reusable test patterns (setup, assertions, fixtures): `npx ai-devkit@latest memory store --title "<pattern>" --content "<details>" --tags "tdd,testing"`

skills/verify/SKILL.md

@@ -64,4 +64,4 @@ If step 4 passes, the test is wrong. Rewrite it.
 
 ## Memory Integration
 
-After a failed verification, store the failure pattern via the `memory` skill with tags `verify,failure-pattern` so future sessions can avoid the same mistake.
+After a failed verification, store the failure pattern: `npx ai-devkit@latest memory store --title "<failure pattern>" --content "<what failed and how to avoid>" --tags "verify,failure-pattern"`