midas-mcp 1.8.0 → 2.2.0

package/docs/USER_RULES.md

@@ -1,90 +1,71 @@
-# User Rules Reference
+# Midas - Cursor User Rules
 
-Expert user rules for .cursorrules files.
+Add these rules to your **Cursor User Rules** (Settings → Rules for AI) to make Cursor automatically follow the Golden Code methodology across ALL projects.
 
----
+## The Rules to Add
 
-## Documentation Style
-
-- No emojis, no ALL CAPS, no markdown tables with dashes/pipes
-- No em dashes, no excessive formatting
-- Bold key words inside sentences for emphasis
-- Write tersely, casually, high IQ
-
----
-
-## Paid Services (Firebase, APIs, etc.)
-
-- **SHOW THE MATH** - Calculate and comment max monthly cost
-- **LIMIT EVERYTHING** - No operation without explicit maximum
-- **PREVENT LOOPS** - Code must not trigger itself without guards
-
----
-
-## Security
-
-- Build exhaustively secure, unhackable
-- Comprehensive .gitignore from day 1
-- Production-ready always
-- Never git push an API key
-
----
-
-## Code Quality
-
-- Single responsibility principle
-- Achieve each task in minimum tokens
-- Testflight-deployable builds
-- Add logs and look up documentation to debug
-
----
-
-## Workflow
-
-- Don't delete scripts when done, move to scripts folder
-- Try to compile/build before git committing, fix errors as needed
-- Simple short git commit after changes, no emojis or special characters
-- Deploy Firebase rules/functions/indexes when changed
-- Deploy Firebase cloud functions when updated
-
----
-
-## Testing
-
-- Use iPhone 16 or 16 Pro for Xcode iOS simulator
-
----
-
-## Full Rules Template
+```
+# Golden Code Methodology (via Midas MCP)
+
+## AUTOMATIC BEHAVIOR - Do these without being asked:
+
+### On EVERY new chat session:
+1. Call `midas_journal_list` to load context from previous sessions
+2. Call `midas_analyze` to understand current project phase
+3. Follow the suggested approach from the analysis
+
+### After EVERY significant code change:
+1. Git commit with descriptive message before AND after major changes
+2. Call `midas_journal_save` with title describing what was done
+3. Include the full conversation in the journal entry
+
+### Before EVERY implementation:
+1. Call `midas_suggest_prompt` to get phase-appropriate guidance
+2. Follow the Golden Code methodology for current phase
+
+## When Things Go Wrong:
+- **Stuck/confused**: Call `midas_tornado` for Research + Logs + Tests cycle
+- **Output doesn't fit**: Call `midas_horizon` to expand context
+- **Retry after error**: Call `midas_oneshot` to construct better retry
+
+## Git Discipline:
+- Commit BEFORE starting any significant change (checkpoint)
+- Commit AFTER completing each logical unit of work
+- Use descriptive commit messages that explain WHY not just WHAT
+
+## The 7-Step BUILD Cycle:
+RULES → INDEX → READ → RESEARCH → IMPLEMENT → TEST → DEBUG
+Always complete earlier steps before jumping to implementation.
+
+## The 4 Phases:
+1. EAGLE_SIGHT: Plan before coding (brainlift, PRD, gameplan)
+2. BUILD: The 7-step cycle above
+3. SHIP: Review, deploy, monitor
+4. GROW: Feedback, analyze, iterate back to EAGLE_SIGHT
+```
 
-```plaintext
-# DOCUMENTATION
-- No emojis, no ALL CAPS, no tables with dashes/pipes
-- No em dashes, no excessive formatting
-- Bold for emphasis, write tersely, casually, high IQ
+## How to Add
 
-# PAID SERVICES
-- SHOW THE MATH - Calculate and comment max monthly cost
-- LIMIT EVERYTHING - No operation without explicit maximum
-- PREVENT LOOPS - Code must not trigger itself without guards
+1. Open Cursor Settings (Cmd+,)
+2. Search for "Rules for AI" or navigate to it
+3. Paste the rules above
+4. Save
 
-# SECURITY
-- Build exhaustively secure, unhackable
-- Comprehensive .gitignore from day 1
-- Production-ready always
-- Never git push an API key
+Now Cursor will automatically:
+- Load journal context at session start
+- Analyze project phase
+- Save conversations to journal
+- Git commit before/after changes
+- Follow the Golden Code methodology
 
-# CODE QUALITY
-- Single responsibility principle
-- Achieve each task in minimum tokens
-- Add logs and look up documentation to debug
+## Why User Rules Instead of .cursorrules
 
-# WORKFLOW
-- Don't delete scripts, move to scripts folder
-- Compile/build before git committing
-- Simple short git commit, no emojis or special characters
-- Deploy Firebase rules/functions/indexes when changed
+| Feature | User Rules | .cursorrules |
+|---------|-----------|--------------|
+| Scope | All projects | One project |
+| Git tracked | No | Yes |
+| Setup | Once | Per project |
+| Override | Per-project can override | N/A |
 
-# TESTING
-- Use iPhone 16 or 16 Pro for Xcode iOS simulator
-```
+User Rules are ideal for methodology/workflow rules that should apply everywhere.
+Project `.cursorrules` are for project-specific conventions (TypeScript config, naming, etc).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "midas-mcp",
-  "version": "1.8.0",
+  "version": "2.2.0",
   "description": "MCP server for Golden Code methodology - everything you vibecode turns to gold",
   "main": "dist/index.js",
   "bin": {