@grec0/memory-bank-mcp 0.2.1 → 0.2.3

package/dist/common/projectKnowledgeService.js

@@ -1034,17 +1034,23 @@ ${techContext ? `TECHNICAL CONTEXT:\n${techContext.content}` : ''}
 Extract the following information in JSON format:
 {
   "description": "A concise 1-2 sentence description of what this project does",
-  "responsibilities": ["List of 3-5 specific things this project is responsible for"],
-  "owns": ["File patterns or types this project owns, e.g., '*DTO.ts', 'services/', 'controllers/'"],
+  "responsibilities": ["List ALL functional responsibilities - what this project DOES as capabilities/features"],
+  "owns": ["File patterns or directories this project owns, e.g., 'src/services/', '*DTO.ts', 'controllers/'"],
   "projectType": "One of: api, library, frontend, backend, cli, service, monorepo, fullstack",
   "exports": "Package name if it's a library (e.g., '@company/lib-dtos'), or null if not applicable",
-  "keywords": ["5-8 keywords describing this project"]
+  "keywords": ["Relevant keywords describing this project"]
 }
 
-IMPORTANT:
-- Be specific about responsibilities - they help the orchestrator decide where code belongs
-- For "owns", think about what file patterns ONLY this project should create
-- If it's a library, identify what it exports/provides to other projects
+CRITICAL GUIDELINES:
+- responsibilities: List ALL functional capabilities - what this project DOES, NOT how it does it
+  - ✅ GOOD: "Index codebases into vector embeddings", "Provide semantic search over code"
+  - ❌ BAD: "Uses tree-sitter for parsing", "Runs Jest tests", "Documents caveats in README"
+  - Focus on FEATURES and CAPABILITIES, not implementation details, configuration, testing, or documentation
+- owns: List directories/patterns this project creates or modifies (not every file it contains)
+  - ✅ GOOD: "src/tools/", ".memorybank/", "src/services/"
+  - ❌ BAD: "README.md", "package.json", "tsconfig.json" (these are generic project files)
+- Be thorough on functional responsibilities - missing ones cause incorrect task routing
+- Ignore implementation details, CI/CD, testing setup, documentation practices
 
 Respond ONLY with the JSON object, no markdown or explanation.`;
         try {

package/dist/common/version.js

@@ -1,2 +1,2 @@
 // Version of the MCP Kanban server
-export const VERSION = "0.2.1";
+export const VERSION = "0.2.3";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@grec0/memory-bank-mcp",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "MCP server for semantic code indexing with Memory Bank - AI-powered codebase understanding",
   "license": "MIT",
   "author": "@grec0",