@unifiedmemory/cli 1.3.14 → 1.3.15

package/lib/memory-instructions.js

@@ -1,82 +1,76 @@
 // Unique marker to detect if instructions already present
-export const MEMORY_INSTRUCTIONS_MARKER = '<!-- UNIFIEDMEMORY_INSTRUCTIONS_V2 -->';
+export const MEMORY_INSTRUCTIONS_MARKER = '<!-- UNIFIEDMEMORY_INSTRUCTIONS_V3 -->';
 
 export function getMemoryInstructions() {
   return `${MEMORY_INSTRUCTIONS_MARKER}
 
-# UnifiedMemory Integration (REQUIRED)
+# STOP - Read Before ANY Code Task
 
-This project uses UnifiedMemory for persistent knowledge management. The \`unifiedmemory\` MCP server is configured and MUST be used for all relevant queries.
+**MANDATORY**: Call \`search_notes\` BEFORE writing any code. Always. No exceptions.
 
-## Available Tools
+## Pre-Implementation Checklist
 
-The \`unifiedmemory\` MCP server provides these tools (call them like any MCP tool):
+Before ANY coding task, you MUST:
+- [ ] Call \`search_notes\` with relevant keywords
+- [ ] Review results for existing patterns/decisions
+- [ ] Mention what you found (or didn't) in your response
+- [ ] THEN start implementation
 
-| Tool | Purpose | Required Parameters |
-|------|---------|---------------------|
-| \`search_notes\` | **Primary tool** - Search project knowledge base | \`query\` (search text) |
-| \`create_note\` | Record decisions, plans, or completions | \`summary_text\`, \`topic\` |
-| \`list_notes\` | List all notes in current project | None |
-| \`get_note\` | Retrieve a specific note by ID | \`note_id\` |
-| \`list_topics\` | List available topics/categories | None |
-| \`create_topic\` | Create a new topic for organization | \`name\` |
-| \`list_projects\` | List available projects | None |
+---
 
-All tools automatically use the correct project context - no additional configuration needed.
+## WRONG
 
-## MANDATORY: Search Before Implementing
+\`\`\`
+User: "Create a calculator app"
+Assistant: [immediately writes code]  ← NEVER DO THIS
+\`\`\`
 
-**REQUIREMENT**: Before responding to ANY coding task, feature request, or implementation question, you MUST:
+## CORRECT
 
-1. Call the \`search_notes\` tool with the user's query or relevant keywords
-2. Review returned results for prior decisions, patterns, or context
-3. Incorporate relevant findings into your response
-4. Mention what context you found (or didn't find) in your response
+\`\`\`
+User: "Create a calculator app"
+Assistant: [calls search_notes first]
+Assistant: "No relevant patterns found in UnifiedMemory. Proceeding..."
+Assistant: [writes code]
+\`\`\`
 
-### When to Search
+---
 
-You MUST search before:
-- Implementing any feature (search for existing patterns)
-- Fixing any bug (search for related issues)
-- Answering architecture questions (search for design decisions)
-- Modifying any component (search for existing conventions)
-- ANY coding task, no exceptions
+## When to Search (ALWAYS)
 
-### Example Workflow
+- Before implementing ANY feature ← search first
+- Before fixing ANY bug ← search first
+- Before answering architecture questions ← search first
+- Before modifying ANY component ← search first
+- For "simple" tasks ← search first (context always helps)
 
-\`\`\`
-User: "Add authentication to the API"
-
-Step 1: Call search_notes with query "authentication API security"
-Step 2: Review results - found: "Decision: Use JWT with refresh tokens"
-Step 3: Implement following the established pattern
-Step 4: Respond: "Based on prior decisions in UnifiedMemory, I'll use JWT..."
-\`\`\`
+---
 
-## Do NOT Skip These Tools
+## MCP Tool Reference
 
-- ❌ NEVER start implementing without calling \`search_notes\` first
-- ❌ NEVER assume patterns without checking the knowledge base
-- ❌ NEVER skip search for "simple" tasks - context always helps
-- ✅ ALWAYS search even if you think you know the answer
-- ✅ ALWAYS mention search results (or lack thereof) in your response
-- ✅ ALWAYS use these tools when they can provide relevant context
+| Tool | Purpose | Parameters |
+|------|---------|------------|
+| \`search_notes\` | **Search knowledge base** | \`body: {q: "search text"}\` |
+| \`create_note\` | Record decisions/completions | \`body: {summary_text: "...", topic: "..."}\` |
+| \`list_notes\` | Browse all notes | None |
+| \`get_note\` | Get note by ID | \`body: {note_id: "..."}\` |
+| \`list_topics\` | List categories | None |
+| \`create_topic\` | Create category | \`body: {name: "..."}\` |
 
-## Recording Knowledge with create_note
+Project context is automatic - no extra config needed.
 
-After completing significant work, use \`create_note\` to record:
-- Implementation decisions and rationale
-- Completed features or fixes
-- Architectural patterns established
-- Gotchas or lessons learned
+---
 
-Keep notes concise (under 1000 characters) and focus on the "why" not the "what".
+## After Completing Work
 
-## Additional Tools
+Use \`create_note\` to record:
+- Decisions and rationale (the "why")
+- Patterns established
+- Gotchas or lessons learned
 
-Use \`list_topics\` to understand project organization, \`list_notes\` to browse available knowledge, and \`get_note\` to retrieve full details of relevant notes found via search.
+Keep notes under 1000 chars. Focus on "why" not "what".
 
 ---
-*UnifiedMemory CLI - Knowledge that persists*
+*UnifiedMemory - \`search_notes\` FIRST, code SECOND*
 `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unifiedmemory/cli",
-  "version": "1.3.14",
+  "version": "1.3.15",
   "description": "UnifiedMemory CLI - AI code assistant integration",
   "main": "index.js",
   "type": "module",