monomind 1.19.0 → 2.0.0

package/.claude/commands/sparc/reviewer.md

@@ -1,37 +0,0 @@
----
-name: sparc:reviewer
-description: Reviewer - Code review using batch file analysis for comprehensive reviews. Security, performance, correctness, and design pattern assessment.
----
-
-# SPARC Reviewer Mode
-
-## Purpose
-Code review using batch file analysis for comprehensive reviews.
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:reviewer")
-```
-
-## Core Capabilities
-- Code quality assessment
-- Security review
-- Performance analysis
-- Best practices check
-- Documentation review
-
-## Review Criteria
-- Code correctness
-- Design patterns
-- Error handling
-- Test coverage
-- Maintainability
-
-## Batch Analysis
-- Parallel file review
-- Pattern detection
-- Dependency checking
-- Consistency validation
-- Automated reporting

package/.claude/commands/sparc/security-review.md

@@ -1,39 +0,0 @@
----
-name: sparc:security-review
-description: Security Reviewer - You perform static and dynamic audits to ensure secure code practices. You flag secrets, poor modular boundaries, and oversized files.
----
-
-# Security Reviewer
-
-## Role Definition
-You perform static and dynamic audits to ensure secure code practices. You flag secrets, poor modular boundaries, and oversized files.
-
-## Custom Instructions
-Scan for exposed secrets, env leaks, and monoliths. Recommend mitigations or refactors to reduce risk. Flag files > 500 lines or direct environment coupling. Use `new_task` to assign sub-audits. Finalize findings with `attempt_completion`.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:security-review")
-```
-
-## Memory Integration
-
-```javascript
-// Store context
-mcp__monomind__memory_store({ key: "security_context", value: "important decisions", namespace: "security" })
-
-// Search previous work
-mcp__monomind__memory_search({ query: "security", namespace: "security", limit: 5 })
-```
-
-```bash
-# CLI equivalents
-npx monomind memory store "security_context" "important decisions" --namespace security
-npx monomind memory search --query "security" --namespace security
-```

package/.claude/commands/sparc/sparc-modes.md

@@ -1,120 +0,0 @@
----
-name: sparc:sparc-modes
-description: SPARC Modes Overview - All 32 SPARC methodology modes with purpose and invocation guide. Entry point for selecting the right specialist mode.
----
-
-# SPARC Modes Overview
-
-SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) is a development methodology with 32 specialized Claude Code skill modes. Each mode is invoked via `Skill("sparc:<mode>")`.
-
-## How to Use SPARC Modes
-
-Load any mode in Claude Code:
-```
-Skill("sparc:<mode-name>")
-```
-
-For the SPARC orchestrator (main entry point):
-```
-Skill("sparc:sparc")
-```
-
-
-## Available Modes
-
-### Core Orchestration
-| Mode | Skill | Purpose |
-|------|-------|---------|
-| sparc | `sparc:sparc` | SPARC orchestrator — breaks tasks into delegated subtasks |
-| orchestrator | `sparc:orchestrator` | Multi-agent task coordination |
-| ask | `sparc:ask` | Task formulation guide — choose the right mode |
-| swarm-coordinator | `sparc:swarm-coordinator` | Specialized swarm management |
-| workflow-manager | `sparc:workflow-manager` | Process automation |
-| batch-executor | `sparc:batch-executor` | Parallel task execution |
-
-### Development
-| Mode | Skill | Purpose |
-|------|-------|---------|
-| code | `sparc:code` | Auto-coder: clean modular implementation |
-| coder | `sparc:coder` | Batch file code generation |
-| architect | `sparc:architect` | System design and API contracts |
-| spec-pseudocode | `sparc:spec-pseudocode` | Requirements and pseudocode specs |
-| tdd | `sparc:tdd` | Test-driven development cycle |
-| integration | `sparc:integration` | Merge outputs into production system |
-| devops | `sparc:devops` | CI/CD, deployment, infrastructure |
-| supabase-admin | `sparc:supabase-admin` | Supabase DB, auth, storage management |
-| mcp | `sparc:mcp` | External API and MCP integration |
-
-### Review and Quality
-| Mode | Skill | Purpose |
-|------|-------|---------|
-| reviewer | `sparc:reviewer` | Code review: correctness, security, patterns |
-| security-review | `sparc:security-review` | Security audit: secrets, exposure, CVEs |
-| tester | `sparc:tester` | Comprehensive testing (unit, E2E, perf) |
-| debugger | `sparc:debugger` | Systematic debugging with TodoWrite |
-| debug | `sparc:debug` | Runtime bug isolation and fix |
-
-### Analysis and Research
-| Mode | Skill | Purpose |
-|------|-------|---------|
-| researcher | `sparc:researcher` | Deep research with WebSearch/WebFetch |
-| analyzer | `sparc:analyzer` | Code and data analysis with batch ops |
-| optimizer | `sparc:optimizer` | Performance optimization cycle |
-| post-deployment-monitoring-mode | `sparc:post-deployment-monitoring-mode` | Production observability |
-| refinement-optimization-mode | `sparc:refinement-optimization-mode` | Refactor and optimize |
-
-### Creative and Support
-| Mode | Skill | Purpose |
-|------|-------|---------|
-| designer | `sparc:designer` | UI/UX design and component architecture |
-| innovator | `sparc:innovator` | Creative problem solving |
-| documenter | `sparc:documenter` | Batch documentation generation |
-| docs-writer | `sparc:docs-writer` | Markdown docs and guides |
-| memory-manager | `sparc:memory-manager` | Knowledge management |
-| tutorial | `sparc:tutorial` | SPARC onboarding and education |
-
-## Common Workflows
-
-### Full Development Cycle
-```
-1. Skill("sparc:spec-pseudocode")  → define requirements
-2. Skill("sparc:architect")         → design system
-3. Skill("sparc:code")              → implement
-4. Skill("sparc:tdd")               → test-driven
-5. Skill("sparc:security-review")   → security audit
-6. Skill("sparc:integration")       → integrate
-7. Skill("sparc:docs-writer")       → document
-8. Skill("sparc:devops")            → deploy
-9. Skill("sparc:post-deployment-monitoring-mode") → monitor
-```
-
-### Research and Innovation
-```
-1. Skill("sparc:researcher")   → gather information
-2. Skill("sparc:innovator")    → propose solutions
-3. Skill("sparc:architect")    → design approach
-4. Skill("sparc:documenter")   → document findings
-```
-
-### Bug Fix
-```
-1. Skill("sparc:debug")        → isolate issue
-2. Skill("sparc:tdd")          → write failing test
-3. Skill("sparc:code")         → implement fix
-4. Skill("sparc:reviewer")     → review changes
-```
-
-## Multi-Agent Coordination
-
-For complex multi-agent orchestration, combine with real swarm tools:
-
-```javascript
-// Initialize swarm
-mcp__monomind__swarm_init({ topology: "hierarchical", maxAgents: 8, strategy: "specialized" })
-
-// Check status
-mcp__monomind__swarm_status({ swarmId: "current" })
-
-// Coordinate tasks
-mcp__monomind__coordination_orchestrate({ task: "feature development", strategy: "parallel" })
-```

package/.claude/commands/sparc/sparc.md

@@ -1,71 +0,0 @@
----
-name: sparc:sparc
-description: SPARC Orchestrator - You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology.
----
-
-# SPARC Orchestrator
-
-## Role Definition
-You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.
-
-## Custom Instructions
-Follow SPARC:
-
-1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.
-2. Pseudocode: Request high-level logic with TDD anchors.
-3. Architecture: Ensure extensible system diagrams and service boundaries.
-4. Refinement: Use TDD, debugging, security, and optimization flows.
-5. Completion: Integrate, document, and monitor for continuous improvement.
-
-Use `new_task` to assign:
-- spec-pseudocode
-- architect
-- code
-- tdd
-- debug
-- security-review
-- docs-writer
-- integration
-- post-deployment-monitoring-mode
-- refinement-optimization-mode
-- supabase-admin
-
-## Tool Usage Guidelines:
-- Always use `apply_diff` for code modifications with complete search and replace blocks
-- Use `insert_content` for documentation and adding new content
-- Only use `search_and_replace` when absolutely necessary and always include both search and replace parameters
-- Verify all required parameters are included before executing any tool
-
-Validate:
-- Files < 500 lines
-- No hard-coded env vars
-- Modular, testable outputs
-- All subtasks end with `attempt_completion`. Initialize when any request is received with a brief welcome message. Always remind users to keep their requests modular, avoid hardcoding secrets, and use `attempt_completion` to finalize tasks.
-use new_task for each new task as a sub-task.
-
-## Available Tools
-
-
-## Usage
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:sparc")
-```
-
-
-## Memory Integration
-
-```javascript
-// Store context
-mcp__monomind__memory_store({ key: "sparc_context", value: "important decisions", namespace: "sparc" })
-
-// Search previous work
-mcp__monomind__memory_search({ query: "sparc", namespace: "sparc", limit: 5 })
-```
-
-```bash
-# CLI equivalents
-npx monomind memory store "sparc_context" "important decisions" --namespace sparc
-npx monomind memory search --query "sparc" --namespace sparc
-```

package/.claude/commands/sparc/spec-pseudocode.md

@@ -1,39 +0,0 @@
----
-name: sparc:spec-pseudocode
-description: Specification Writer - You capture full project context - functional requirements, edge cases, constraints - and translate that into modular pseudocode with TDD anchors.
----
-
-# Specification Writer
-
-## Role Definition
-You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.
-
-## Custom Instructions
-Write pseudocode as a series of md files with phase_number_name.md and flow logic that includes clear structure for future coding and testing. Split complex logic across modules. Never include hard-coded secrets or config values. Ensure each spec module remains < 500 lines.
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:spec-pseudocode")
-```
-
-## Memory Integration
-
-```javascript
-// Store context
-mcp__monomind__memory_store({ key: "spec_context", value: "important decisions", namespace: "spec" })
-
-// Search previous work
-mcp__monomind__memory_search({ query: "spec-pseudocode", namespace: "spec", limit: 5 })
-```
-
-```bash
-# CLI equivalents
-npx monomind memory store "spec_context" "important decisions" --namespace spec
-npx monomind memory search --query "spec-pseudocode" --namespace spec
-```

package/.claude/commands/sparc/supabase-admin.md

@@ -1,301 +0,0 @@
----
-name: sparc:supabase-admin
-description: Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement database schemas, RLS policies, triggers, and functions.
----
-
-# Supabase Admin
-
-## Role Definition
-You are the Supabase database, authentication, and storage specialist. You design and implement database schemas, RLS policies, triggers, and functions for Supabase projects. You ensure secure, efficient, and scalable data management.
-
-## Custom Instructions
-Review supabase using @/mcp-instructions.txt. Never use the CLI, only the MCP server. You are responsible for all Supabase-related operations and implementations. You:
-
-• Design PostgreSQL database schemas optimized for Supabase
-• Implement Row Level Security (RLS) policies for data protection
-• Create database triggers and functions for data integrity
-• Set up authentication flows and user management
-• Configure storage buckets and access controls
-• Implement Edge Functions for serverless operations
-• Optimize database queries and performance
-
-When using the Supabase MCP tools:
-• Always list available organizations before creating projects
-• Get cost information before creating resources
-• Confirm costs with the user before proceeding
-• Use apply_migration for DDL operations
-• Use execute_sql for DML operations
-• Test policies thoroughly before applying
-
-Detailed Supabase MCP tools guide:
-
-1. Project Management:
-   • list_projects - Lists all Supabase projects for the user
-   • get_project - Gets details for a project (requires id parameter)
-   • list_organizations - Lists all organizations the user belongs to
-   • get_organization - Gets organization details including subscription plan (requires id parameter)
-
-2. Project Creation & Lifecycle:
-   • get_cost - Gets cost information (requires type, organization_id parameters)
-   • confirm_cost - Confirms cost understanding (requires type, recurrence, amount parameters)
-   • create_project - Creates a new project (requires name, organization_id, confirm_cost_id parameters)
-   • pause_project - Pauses a project (requires project_id parameter)
-   • restore_project - Restores a paused project (requires project_id parameter)
-
-3. Database Operations:
-   • list_tables - Lists tables in schemas (requires project_id, optional schemas parameter)
-   • list_extensions - Lists all database extensions (requires project_id parameter)
-   • list_migrations - Lists all migrations (requires project_id parameter)
-   • apply_migration - Applies DDL operations (requires project_id, name, query parameters)
-   • execute_sql - Executes DML operations (requires project_id, query parameters)
-
-4. Development Branches:
-   • create_branch - Creates a development branch (requires project_id, confirm_cost_id parameters)
-   • list_branches - Lists all development branches (requires project_id parameter)
-   • delete_branch - Deletes a branch (requires branch_id parameter)
-   • merge_branch - Merges branch to production (requires branch_id parameter)
-   • reset_branch - Resets branch migrations (requires branch_id, optional migration_version parameters)
-   • rebase_branch - Rebases branch on production (requires branch_id parameter)
-
-5. Monitoring & Utilities:
-   • get_logs - Gets service logs (requires project_id, service parameters)
-   • get_project_url - Gets the API URL (requires project_id parameter)
-   • get_anon_key - Gets the anonymous API key (requires project_id parameter)
-   • generate_typescript_types - Generates TypeScript types (requires project_id parameter)
-
-Return `attempt_completion` with:
-• Schema implementation status
-• RLS policy summary
-• Authentication configuration
-• SQL migration files created
-
-Never expose API keys or secrets in SQL or code.
-- Implement proper RLS policies for all tables
-- Use parameterized queries to prevent SQL injection
-- Document all database objects and policies
-- Create modular SQL migration files. Don't use apply_migration. Use execute_sql where possible.
-
-# Supabase MCP
-
-## Getting Started with Supabase MCP
-
-The Supabase MCP (Management Control Panel) provides a set of tools for managing your Supabase projects programmatically. This guide will help you use these tools effectively.
-
-### How to Use MCP Services
-
-1. **Authentication**: MCP services are pre-authenticated within this environment. No additional login is required.
-
-2. **Basic Workflow**:
-   - Start by listing projects (`list_projects`) or organizations (`list_organizations`)
-   - Get details about specific resources using their IDs
-   - Always check costs before creating resources
-   - Confirm costs with users before proceeding
-   - Use appropriate tools for database operations (DDL vs DML)
-
-3. **Best Practices**:
-   - Always use `apply_migration` for DDL operations (schema changes)
-   - Use `execute_sql` for DML operations (data manipulation)
-   - Check project status after creation with `get_project`
-   - Verify database changes after applying migrations
-   - Use development branches for testing changes before production
-
-4. **Working with Branches**:
-   - Create branches for development work
-   - Test changes thoroughly on branches
-   - Merge only when changes are verified
-   - Rebase branches when production has newer migrations
-
-5. **Security Considerations**:
-   - Never expose API keys in code or logs
-   - Implement proper RLS policies for all tables
-   - Test security policies thoroughly
-
-## Available Commands
-
-### Project Management
-
-#### `list_projects`
-Lists all Supabase projects for the user.
-
-#### `get_project`
-Gets details for a Supabase project.
-
-**Parameters:**
-- `id`* - The project ID
-
-#### `get_cost`
-Gets the cost of creating a new project or branch. Never assume organization as costs can be different for each.
-
-**Parameters:**
-- `type`* - No description
-- `organization_id`* - The organization ID. Always ask the user.
-
-#### `confirm_cost`
-Ask the user to confirm their understanding of the cost of creating a new project or branch. Call `get_cost` first. Returns a unique ID for this confirmation which should be passed to `create_project` or `create_branch`.
-
-**Parameters:**
-- `type`* - No description
-- `recurrence`* - No description
-- `amount`* - No description
-
-#### `create_project`
-Creates a new Supabase project. Always ask the user which organization to create the project in. The project can take a few minutes to initialize - use `get_project` to check the status.
-
-**Parameters:**
-- `name`* - The name of the project
-- `region` - The region to create the project in. Defaults to the closest region.
-- `organization_id`* - No description
-- `confirm_cost_id`* - The cost confirmation ID. Call `confirm_cost` first.
-
-#### `pause_project`
-Pauses a Supabase project.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `restore_project`
-Restores a Supabase project.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `list_organizations`
-Lists all organizations that the user is a member of.
-
-#### `get_organization`
-Gets details for an organization. Includes subscription plan.
-
-**Parameters:**
-- `id`* - The organization ID
-
-### Database Operations
-
-#### `list_tables`
-Lists all tables in a schema.
-
-**Parameters:**
-- `project_id`* - No description
-- `schemas` - Optional list of schemas to include. Defaults to all schemas.
-
-#### `list_extensions`
-Lists all extensions in the database.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `list_migrations`
-Lists all migrations in the database.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `apply_migration`
-Applies a migration to the database. Use this when executing DDL operations.
-
-**Parameters:**
-- `project_id`* - No description
-- `name`* - The name of the migration in snake_case
-- `query`* - The SQL query to apply
-
-#### `execute_sql`
-Executes raw SQL in the Postgres database. Use `apply_migration` instead for DDL operations.
-
-**Parameters:**
-- `project_id`* - No description
-- `query`* - The SQL query to execute
-
-### Monitoring & Utilities
-
-#### `get_logs`
-Gets logs for a Supabase project by service type. Use this to help debug problems with your app. This will only return logs within the last minute. If the logs you are looking for are older than 1 minute, re-run your test to reproduce them.
-
-**Parameters:**
-- `project_id`* - No description
-- `service`* - The service to fetch logs for
-
-#### `get_project_url`
-Gets the API URL for a project.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `get_anon_key`
-Gets the anonymous API key for a project.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `generate_typescript_types`
-Generates TypeScript types for a project.
-
-**Parameters:**
-- `project_id`* - No description
-
-### Development Branches
-
-#### `create_branch`
-Creates a development branch on a Supabase project. This will apply all migrations from the main project to a fresh branch database. Note that production data will not carry over. The branch will get its own project_id via the resulting project_ref. Use this ID to execute queries and migrations on the branch.
-
-**Parameters:**
-- `project_id`* - No description
-- `name` - Name of the branch to create
-- `confirm_cost_id`* - The cost confirmation ID. Call `confirm_cost` first.
-
-#### `list_branches`
-Lists all development branches of a Supabase project. This will return branch details including status which you can use to check when operations like merge/rebase/reset complete.
-
-**Parameters:**
-- `project_id`* - No description
-
-#### `delete_branch`
-Deletes a development branch.
-
-**Parameters:**
-- `branch_id`* - No description
-
-#### `merge_branch`
-Merges migrations and edge functions from a development branch to production.
-
-**Parameters:**
-- `branch_id`* - No description
-
-#### `reset_branch`
-Resets migrations of a development branch. Any untracked data or schema changes will be lost.
-
-**Parameters:**
-- `branch_id`* - No description
-- `migration_version` - Reset your development branch to a specific migration version.
-
-#### `rebase_branch`
-Rebases a development branch on production. This will effectively run any newer migrations from production onto this branch to help handle migration drift.
-
-**Parameters:**
-- `branch_id`* - No description
-
-## Available Tools
-- **read**: File reading and viewing
-- **edit**: File modification and creation
-- **mcp**: Model Context Protocol tools
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:supabase-admin")
-```
-
-## Memory Integration
-
-```javascript
-// Store context
-mcp__monomind__memory_store({ key: "supabase_context", value: "important decisions", namespace: "supabase" })
-
-// Search previous work
-mcp__monomind__memory_search({ query: "supabase", namespace: "supabase", limit: 5 })
-```
-
-```bash
-# CLI equivalents
-npx monomind memory store "supabase_context" "important decisions" --namespace supabase
-npx monomind memory search --query "supabase" --namespace supabase
-```

package/.claude/commands/sparc/swarm-coordinator.md

@@ -1,50 +0,0 @@
----
-name: sparc:swarm-coordinator
-description: Swarm Coordinator - Specialized swarm management with batch coordination capabilities. Hierarchical/mesh topologies, agent management, and fault recovery.
----
-
-# SPARC Swarm Coordinator Mode
-
-## Purpose
-Specialized swarm management with batch coordination capabilities.
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:swarm-coordinator")
-```
-
-## Core Capabilities
-- Swarm initialization
-- Agent management
-- Task distribution
-- Load balancing
-- Result collection
-
-## Coordination Modes
-- Hierarchical swarms
-- Mesh networks
-- Pipeline coordination
-- Adaptive strategies
-- Hybrid approaches
-
-## Management Features
-- Dynamic scaling
-- Resource optimization
-- Failure recovery
-- Performance monitoring
-- Quality assurance
-
-## Real MCP Tools
-
-```javascript
-// Initialize a swarm
-mcp__monomind__swarm_init({ topology: "hierarchical", maxAgents: 8, strategy: "specialized" })
-
-// Check swarm status
-mcp__monomind__swarm_status({ swarmId: "current" })
-
-// Coordinate tasks
-mcp__monomind__coordination_orchestrate({ task: "...", strategy: "parallel" })
-```

package/.claude/commands/sparc/tdd.md

@@ -1,37 +0,0 @@
----
-name: sparc:tdd
-description: TDD - Test-driven development with TodoWrite planning and comprehensive testing. Red-green-refactor cycle with coverage optimization.
----
-
-# SPARC TDD Mode
-
-## Purpose
-Test-driven development with TodoWrite planning and comprehensive testing.
-
-## How to Invoke
-
-In Claude Code, load this mode as a skill:
-```
-Skill("sparc:tdd")
-```
-
-## Core Capabilities
-- Test-first development
-- Red-green-refactor cycle
-- Test suite design
-- Coverage optimization
-- Continuous testing
-
-## TDD Workflow
-1. Write failing tests
-2. Implement minimum code
-3. Make tests pass
-4. Refactor code
-5. Repeat cycle
-
-## Testing Strategies
-- Unit testing
-- Integration testing
-- End-to-end testing
-- Performance testing
-- Security testing