@10kdevs/matha 0.1.1 → 0.1.3

package/README.md

@@ -162,15 +162,60 @@ matha_get_routing(operationType?)   Learned model routing rules
 ## Initialising From An Existing Document
 
 If your project already has a BRD, spec, or requirements document:
+## Setting Up Your Project Brain
+
+Before running `matha init`, generate a `requirements.md` file that 
+captures your project's intent, rules, and boundaries in a format 
+MATHA understands deeply.
+
+**Paste this prompt into any AI assistant:**
+```
+I am setting up MATHA — a persistent cognitive layer for AI-assisted 
+development. I need you to generate a requirements.md file for my 
+project that MATHA will parse during initialisation.
+
+My project: [describe your project in 2-3 sentences]
+
+Generate a requirements.md with exactly these sections:
+
+## Overview
+A concise paragraph explaining what problem this project solves 
+and why it exists. Focus on the WHY, not the features.
+
+## Business Rules
+A bullet list of non-negotiable rules that must always be true.
+These are constraints the codebase must never violate.
+Examples: calculation logic, data integrity rules, 
+financial constraints, domain-specific invariants.
+
+## Out of Scope
+A bullet list of things this project explicitly does NOT do.
+These are boundaries that protect the system from scope creep.
+
+## Owner
+The name or team responsible for this project.
+
+Be specific and precise. Vague rules are useless. 
+Each rule should be concrete enough that a developer 
+who has never seen the codebase understands exactly 
+what it means.
+```
+
+Then run:
 
 ```bash
 matha init --from requirements.md
 ```
 
+MATHA will parse the document, show you what it found, 
+and let you confirm or override before writing anything.
+
+
 MATHA parses business rules, boundaries, and intent from the document and pre-fills the init prompts. You review and confirm. Nothing is written without your sign-off.
 
 ---
 
+
 ## What MATHA Is Not
 
 MATHA does not generate code.

package/dist/commands/init.js

@@ -132,6 +132,28 @@ export async function runInit(projectRoot = process.cwd(), deps) {
     catch {
         log('No git history found — cortex will build as commits accumulate');
     }
+    // Write MCP server config
+    try {
+        const mcpServerPath = await resolveMcpServerPath(projectRoot);
+        const mcpConfigContent = {
+            mcpServers: {
+                matha: {
+                    command: 'node',
+                    args: [mcpServerPath, 'serve'],
+                    description: 'MATHA persistent cognitive layer',
+                },
+            },
+        };
+        const mcpConfigPath = path.join(mathaDir, 'mcp-config.json');
+        await writeAtomic(mcpConfigPath, mcpConfigContent, { overwrite: true });
+        log('');
+        log('MCP server config written to .matha/mcp-config.json');
+        log('Add this to your IDE MCP settings:');
+        log(JSON.stringify(mcpConfigContent, null, 2));
+    }
+    catch (err) {
+        log(`Warning: Could not write MCP config: ${err.message}`);
+    }
     return {
         projectRoot,
         brainDir: '.matha',
@@ -264,3 +286,13 @@ async function defaultAsk(message) {
     const prompts = await import('@inquirer/prompts');
     return prompts.input({ message });
 }
+async function resolveMcpServerPath(projectRoot) {
+    // Try node_modules/.bin/matha first
+    const npmBinPath = path.join(projectRoot, 'node_modules', '.bin', 'matha');
+    if (await pathExists(npmBinPath)) {
+        return npmBinPath;
+    }
+    // Fall back to dist/index.js
+    const distPath = path.join(projectRoot, 'dist', 'index.js');
+    return distPath;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@10kdevs/matha",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "The persistent cognitive layer for AI-assisted development. Gives AI agents the project context that currently only exists inside a senior engineer's head.",
   "main": "./dist/index.js",
   "bin": {