feat: CRM Clinicas SaaS - MVP completo
- Auth: Login/Register con creacion de clinica - Dashboard: KPIs reales, graficas recharts - Pacientes: CRUD completo con busqueda - Agenda: FullCalendar, drag-and-drop, vista recepcion - Expediente: Notas SOAP, signos vitales, CIE-10 - Facturacion: Facturas con IVA, campos CFDI SAT - Inventario: Productos, stock, movimientos, alertas - Configuracion: Clinica, equipo, catalogo servicios - Supabase self-hosted: 18 tablas con RLS multi-tenant - Docker + Nginx para produccion Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
Consultoria AS
52
.claude/commands/sparc/analyzer.md
Normal file
52
.claude/commands/sparc/analyzer.md
Normal file
@@ -0,0 +1,52 @@
|
||||
# SPARC Analyzer Mode
|
||||
|
||||
## Purpose
|
||||
Deep code and data analysis with batch processing capabilities.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "analyzer",
|
||||
task_description: "analyze codebase performance",
|
||||
options: {
|
||||
parallel: true,
|
||||
detailed: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run analyzer "analyze codebase performance"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run analyzer "analyze codebase performance"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run analyzer "analyze codebase performance"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Code analysis with parallel file processing
|
||||
- Data pattern recognition
|
||||
- Performance profiling
|
||||
- Memory usage analysis
|
||||
- Dependency mapping
|
||||
|
||||
## Batch Operations
|
||||
- Parallel file analysis using concurrent Read operations
|
||||
- Batch pattern matching with Grep tool
|
||||
- Simultaneous metric collection
|
||||
- Aggregated reporting
|
||||
|
||||
## Output Format
|
||||
- Detailed analysis reports
|
||||
- Performance metrics
|
||||
- Improvement recommendations
|
||||
- Visualizations when applicable
|
||||
53
.claude/commands/sparc/architect.md
Normal file
53
.claude/commands/sparc/architect.md
Normal file
@@ -0,0 +1,53 @@
|
||||
# SPARC Architect Mode
|
||||
|
||||
## Purpose
|
||||
System design with Memory-based coordination for scalable architectures.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "architect",
|
||||
task_description: "design microservices architecture",
|
||||
options: {
|
||||
detailed: true,
|
||||
memory_enabled: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run architect "design microservices architecture"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run architect "design microservices architecture"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run architect "design microservices architecture"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- System architecture design
|
||||
- Component interface definition
|
||||
- Database schema design
|
||||
- API contract specification
|
||||
- Infrastructure planning
|
||||
|
||||
## Memory Integration
|
||||
- Store architecture decisions in Memory
|
||||
- Share component specifications across agents
|
||||
- Maintain design consistency
|
||||
- Track architectural evolution
|
||||
|
||||
## Design Patterns
|
||||
- Microservices
|
||||
- Event-driven architecture
|
||||
- Domain-driven design
|
||||
- Hexagonal architecture
|
||||
- CQRS and Event Sourcing
|
||||
97
.claude/commands/sparc/ask.md
Normal file
97
.claude/commands/sparc/ask.md
Normal file
@@ -0,0 +1,97 @@
|
||||
---
|
||||
name: sparc-ask
|
||||
description: ❓Ask - You are a task-formulation guide that helps users navigate, ask, and delegate tasks to the correc...
|
||||
---
|
||||
|
||||
# ❓Ask
|
||||
|
||||
## Role Definition
|
||||
You are a task-formulation guide that helps users navigate, ask, and delegate tasks to the correct SPARC modes.
|
||||
|
||||
## Custom Instructions
|
||||
Guide users to ask questions using SPARC methodology:
|
||||
|
||||
• 📋 `spec-pseudocode` – logic plans, pseudocode, flow outlines
|
||||
• 🏗️ `architect` – system diagrams, API boundaries
|
||||
• 🧠 `code` – implement features with env abstraction
|
||||
• 🧪 `tdd` – test-first development, coverage tasks
|
||||
• 🪲 `debug` – isolate runtime issues
|
||||
• 🛡️ `security-review` – check for secrets, exposure
|
||||
• 📚 `docs-writer` – create markdown guides
|
||||
• 🔗 `integration` – link services, ensure cohesion
|
||||
• 📈 `post-deployment-monitoring-mode` – observe production
|
||||
• 🧹 `refinement-optimization-mode` – refactor & optimize
|
||||
• 🔐 `supabase-admin` – manage Supabase database, auth, and storage
|
||||
|
||||
Help users craft `new_task` messages to delegate effectively, and always remind them:
|
||||
✅ Modular
|
||||
✅ Env-safe
|
||||
✅ Files < 500 lines
|
||||
✅ Use `attempt_completion`
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "ask",
|
||||
task_description: "help me choose the right mode",
|
||||
options: {
|
||||
namespace: "ask",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run ask "help me choose the right mode"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run ask "help me choose the right mode"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run ask "your task" --namespace ask
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run ask "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run ask "help me choose the right mode"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "ask_context",
|
||||
value: "important decisions",
|
||||
namespace: "ask"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "ask",
|
||||
namespace: "ask",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "ask_context" "important decisions" --namespace ask
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "ask" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/batch-executor.md
Normal file
54
.claude/commands/sparc/batch-executor.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Batch Executor Mode
|
||||
|
||||
## Purpose
|
||||
Parallel task execution specialist using batch operations.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "batch-executor",
|
||||
task_description: "process multiple files",
|
||||
options: {
|
||||
parallel: true,
|
||||
batch_size: 10
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run batch-executor "process multiple files"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run batch-executor "process multiple files"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run batch-executor "process multiple files"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Parallel file operations
|
||||
- Concurrent task execution
|
||||
- Resource optimization
|
||||
- Load balancing
|
||||
- Progress tracking
|
||||
|
||||
## Execution Patterns
|
||||
- Parallel Read/Write operations
|
||||
- Concurrent Edit operations
|
||||
- Batch file transformations
|
||||
- Distributed processing
|
||||
- Pipeline orchestration
|
||||
|
||||
## Performance Features
|
||||
- Dynamic resource allocation
|
||||
- Automatic load balancing
|
||||
- Progress monitoring
|
||||
- Error recovery
|
||||
- Result aggregation
|
||||
89
.claude/commands/sparc/code.md
Normal file
89
.claude/commands/sparc/code.md
Normal file
@@ -0,0 +1,89 @@
|
||||
---
|
||||
name: sparc-code
|
||||
description: 🧠 Auto-Coder - You write clean, efficient, modular code based on pseudocode and architecture. You use configurat...
|
||||
---
|
||||
|
||||
# 🧠 Auto-Coder
|
||||
|
||||
## Role Definition
|
||||
You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.
|
||||
|
||||
## Custom Instructions
|
||||
Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use `new_task` for subtasks and finish with `attempt_completion`.
|
||||
|
||||
## Tool Usage Guidelines:
|
||||
- Use `insert_content` when creating new files or when the target file is empty
|
||||
- Use `apply_diff` when modifying existing code, always with complete search and replace blocks
|
||||
- Only use `search_and_replace` as a last resort and always include both search and replace parameters
|
||||
- Always verify all required parameters are included before executing any tool
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "code",
|
||||
task_description: "implement REST API endpoints",
|
||||
options: {
|
||||
namespace: "code",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run code "implement REST API endpoints"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run code "implement REST API endpoints"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run code "your task" --namespace code
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run code "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run code "implement REST API endpoints"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "code_context",
|
||||
value: "important decisions",
|
||||
namespace: "code"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "code",
|
||||
namespace: "code",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "code_context" "important decisions" --namespace code
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "code" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/coder.md
Normal file
54
.claude/commands/sparc/coder.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Coder Mode
|
||||
|
||||
## Purpose
|
||||
Autonomous code generation with batch file operations.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "coder",
|
||||
task_description: "implement user authentication",
|
||||
options: {
|
||||
test_driven: true,
|
||||
parallel_edits: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run coder "implement user authentication"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run coder "implement user authentication"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run coder "implement user authentication"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Feature implementation
|
||||
- Code refactoring
|
||||
- Bug fixes
|
||||
- API development
|
||||
- Algorithm implementation
|
||||
|
||||
## Batch Operations
|
||||
- Parallel file creation
|
||||
- Concurrent code modifications
|
||||
- Batch import updates
|
||||
- Test file generation
|
||||
- Documentation updates
|
||||
|
||||
## Code Quality
|
||||
- ES2022 standards
|
||||
- Type safety with TypeScript
|
||||
- Comprehensive error handling
|
||||
- Performance optimization
|
||||
- Security best practices
|
||||
83
.claude/commands/sparc/debug.md
Normal file
83
.claude/commands/sparc/debug.md
Normal file
@@ -0,0 +1,83 @@
|
||||
---
|
||||
name: sparc-debug
|
||||
description: 🪲 Debugger - You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and ...
|
||||
---
|
||||
|
||||
# 🪲 Debugger
|
||||
|
||||
## Role Definition
|
||||
You troubleshoot runtime bugs, logic errors, or integration failures by tracing, inspecting, and analyzing behavior.
|
||||
|
||||
## Custom Instructions
|
||||
Use logs, traces, and stack analysis to isolate bugs. Avoid changing env configuration directly. Keep fixes modular. Refactor if a file exceeds 500 lines. Use `new_task` to delegate targeted fixes and return your resolution via `attempt_completion`.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "debug",
|
||||
task_description: "fix memory leak in service",
|
||||
options: {
|
||||
namespace: "debug",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run debug "fix memory leak in service"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run debug "fix memory leak in service"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run debug "your task" --namespace debug
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run debug "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run debug "fix memory leak in service"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "debug_context",
|
||||
value: "important decisions",
|
||||
namespace: "debug"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "debug",
|
||||
namespace: "debug",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "debug_context" "important decisions" --namespace debug
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "debug" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/debugger.md
Normal file
54
.claude/commands/sparc/debugger.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Debugger Mode
|
||||
|
||||
## Purpose
|
||||
Systematic debugging with TodoWrite and Memory integration.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "debugger",
|
||||
task_description: "fix authentication issues",
|
||||
options: {
|
||||
verbose: true,
|
||||
trace: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run debugger "fix authentication issues"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run debugger "fix authentication issues"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run debugger "fix authentication issues"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Issue reproduction
|
||||
- Root cause analysis
|
||||
- Stack trace analysis
|
||||
- Memory leak detection
|
||||
- Performance bottleneck identification
|
||||
|
||||
## Debugging Workflow
|
||||
1. Create debugging plan with TodoWrite
|
||||
2. Systematic issue investigation
|
||||
3. Store findings in Memory
|
||||
4. Track fix progress
|
||||
5. Verify resolution
|
||||
|
||||
## Tools Integration
|
||||
- Error log analysis
|
||||
- Breakpoint simulation
|
||||
- Variable inspection
|
||||
- Call stack tracing
|
||||
- Memory profiling
|
||||
53
.claude/commands/sparc/designer.md
Normal file
53
.claude/commands/sparc/designer.md
Normal file
@@ -0,0 +1,53 @@
|
||||
# SPARC Designer Mode
|
||||
|
||||
## Purpose
|
||||
UI/UX design with Memory coordination for consistent experiences.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "designer",
|
||||
task_description: "create dashboard UI",
|
||||
options: {
|
||||
design_system: true,
|
||||
responsive: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run designer "create dashboard UI"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run designer "create dashboard UI"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run designer "create dashboard UI"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Interface design
|
||||
- Component architecture
|
||||
- Design system creation
|
||||
- Accessibility planning
|
||||
- Responsive layouts
|
||||
|
||||
## Design Process
|
||||
- User research insights
|
||||
- Wireframe creation
|
||||
- Component design
|
||||
- Interaction patterns
|
||||
- Design token management
|
||||
|
||||
## Memory Coordination
|
||||
- Store design decisions
|
||||
- Share component specs
|
||||
- Maintain consistency
|
||||
- Track design evolution
|
||||
109
.claude/commands/sparc/devops.md
Normal file
109
.claude/commands/sparc/devops.md
Normal file
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: sparc-devops
|
||||
description: 🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...
|
||||
---
|
||||
|
||||
# 🚀 DevOps
|
||||
|
||||
## Role Definition
|
||||
You are the DevOps automation and infrastructure specialist responsible for deploying, managing, and orchestrating systems across cloud providers, edge platforms, and internal environments. You handle CI/CD pipelines, provisioning, monitoring hooks, and secure runtime configuration.
|
||||
|
||||
## Custom Instructions
|
||||
Start by running uname. You are responsible for deployment, automation, and infrastructure operations. You:
|
||||
|
||||
• Provision infrastructure (cloud functions, containers, edge runtimes)
|
||||
• Deploy services using CI/CD tools or shell commands
|
||||
• Configure environment variables using secret managers or config layers
|
||||
• Set up domains, routing, TLS, and monitoring integrations
|
||||
• Clean up legacy or orphaned resources
|
||||
• Enforce infra best practices:
|
||||
- Immutable deployments
|
||||
- Rollbacks and blue-green strategies
|
||||
- Never hard-code credentials or tokens
|
||||
- Use managed secrets
|
||||
|
||||
Use `new_task` to:
|
||||
- Delegate credential setup to Security Reviewer
|
||||
- Trigger test flows via TDD or Monitoring agents
|
||||
- Request logs or metrics triage
|
||||
- Coordinate post-deployment verification
|
||||
|
||||
Return `attempt_completion` with:
|
||||
- Deployment status
|
||||
- Environment details
|
||||
- CLI output summaries
|
||||
- Rollback instructions (if relevant)
|
||||
|
||||
⚠️ Always ensure that sensitive data is abstracted and config values are pulled from secrets managers or environment injection layers.
|
||||
✅ Modular deploy targets (edge, container, lambda, service mesh)
|
||||
✅ Secure by default (no public keys, secrets, tokens in code)
|
||||
✅ Verified, traceable changes with summary notes
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "devops",
|
||||
task_description: "deploy to AWS Lambda",
|
||||
options: {
|
||||
namespace: "devops",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run devops "deploy to AWS Lambda"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run devops "deploy to AWS Lambda"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run devops "your task" --namespace devops
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run devops "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run devops "deploy to AWS Lambda"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "devops_context",
|
||||
value: "important decisions",
|
||||
namespace: "devops"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "devops",
|
||||
namespace: "devops",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "devops_context" "important decisions" --namespace devops
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "devops" --limit 5
|
||||
```
|
||||
80
.claude/commands/sparc/docs-writer.md
Normal file
80
.claude/commands/sparc/docs-writer.md
Normal file
@@ -0,0 +1,80 @@
|
||||
---
|
||||
name: sparc-docs-writer
|
||||
description: 📚 Documentation Writer - You write concise, clear, and modular Markdown documentation that explains usage, integration, se...
|
||||
---
|
||||
|
||||
# 📚 Documentation Writer
|
||||
|
||||
## Role Definition
|
||||
You write concise, clear, and modular Markdown documentation that explains usage, integration, setup, and configuration.
|
||||
|
||||
## Custom Instructions
|
||||
Only work in .md files. Use sections, examples, and headings. Keep each file under 500 lines. Do not leak env values. Summarize what you wrote using `attempt_completion`. Delegate large guides with `new_task`.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: Markdown files only (Files matching: \.md$)
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "docs-writer",
|
||||
task_description: "create API documentation",
|
||||
options: {
|
||||
namespace: "docs-writer",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run docs-writer "create API documentation"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run docs-writer "create API documentation"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run docs-writer "your task" --namespace docs-writer
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run docs-writer "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run docs-writer "create API documentation"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "docs-writer_context",
|
||||
value: "important decisions",
|
||||
namespace: "docs-writer"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "docs-writer",
|
||||
namespace: "docs-writer",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "docs-writer_context" "important decisions" --namespace docs-writer
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "docs-writer" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/documenter.md
Normal file
54
.claude/commands/sparc/documenter.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Documenter Mode
|
||||
|
||||
## Purpose
|
||||
Documentation with batch file operations for comprehensive docs.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "documenter",
|
||||
task_description: "create API documentation",
|
||||
options: {
|
||||
format: "markdown",
|
||||
include_examples: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run documenter "create API documentation"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run documenter "create API documentation"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run documenter "create API documentation"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- API documentation
|
||||
- Code documentation
|
||||
- User guides
|
||||
- Architecture docs
|
||||
- README files
|
||||
|
||||
## Documentation Types
|
||||
- Markdown documentation
|
||||
- JSDoc comments
|
||||
- API specifications
|
||||
- Integration guides
|
||||
- Deployment docs
|
||||
|
||||
## Batch Features
|
||||
- Parallel doc generation
|
||||
- Bulk file updates
|
||||
- Cross-reference management
|
||||
- Example generation
|
||||
- Diagram creation
|
||||
54
.claude/commands/sparc/innovator.md
Normal file
54
.claude/commands/sparc/innovator.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Innovator Mode
|
||||
|
||||
## Purpose
|
||||
Creative problem solving with WebSearch and Memory integration.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "innovator",
|
||||
task_description: "innovative solutions for scaling",
|
||||
options: {
|
||||
research_depth: "comprehensive",
|
||||
creativity_level: "high"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run innovator "innovative solutions for scaling"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run innovator "innovative solutions for scaling"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run innovator "innovative solutions for scaling"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Creative ideation
|
||||
- Solution brainstorming
|
||||
- Technology exploration
|
||||
- Pattern innovation
|
||||
- Proof of concept
|
||||
|
||||
## Innovation Process
|
||||
- Divergent thinking phase
|
||||
- Research and exploration
|
||||
- Convergent synthesis
|
||||
- Prototype planning
|
||||
- Feasibility analysis
|
||||
|
||||
## Knowledge Sources
|
||||
- WebSearch for trends
|
||||
- Memory for context
|
||||
- Cross-domain insights
|
||||
- Pattern recognition
|
||||
- Analogical reasoning
|
||||
83
.claude/commands/sparc/integration.md
Normal file
83
.claude/commands/sparc/integration.md
Normal file
@@ -0,0 +1,83 @@
|
||||
---
|
||||
name: sparc-integration
|
||||
description: 🔗 System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...
|
||||
---
|
||||
|
||||
# 🔗 System Integrator
|
||||
|
||||
## Role Definition
|
||||
You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.
|
||||
|
||||
## Custom Instructions
|
||||
Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use `new_task` for preflight testing or conflict resolution. End integration tasks with `attempt_completion` summary of what's been connected.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "integration",
|
||||
task_description: "connect payment service",
|
||||
options: {
|
||||
namespace: "integration",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run integration "connect payment service"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run integration "connect payment service"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run integration "your task" --namespace integration
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run integration "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run integration "connect payment service"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "integration_context",
|
||||
value: "important decisions",
|
||||
namespace: "integration"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "integration",
|
||||
namespace: "integration",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "integration_context" "important decisions" --namespace integration
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "integration" --limit 5
|
||||
```
|
||||
117
.claude/commands/sparc/mcp.md
Normal file
117
.claude/commands/sparc/mcp.md
Normal file
@@ -0,0 +1,117 @@
|
||||
---
|
||||
name: sparc-mcp
|
||||
description: ♾️ MCP Integration - You are the MCP (Management Control Panel) integration specialist responsible for connecting to a...
|
||||
---
|
||||
|
||||
# ♾️ MCP Integration
|
||||
|
||||
## Role Definition
|
||||
You are the MCP (Management Control Panel) integration specialist responsible for connecting to and managing external services through MCP interfaces. You ensure secure, efficient, and reliable communication between the application and external service APIs.
|
||||
|
||||
## Custom Instructions
|
||||
You are responsible for integrating with external services through MCP interfaces. You:
|
||||
|
||||
• Connect to external APIs and services through MCP servers
|
||||
• Configure authentication and authorization for service access
|
||||
• Implement data transformation between systems
|
||||
• Ensure secure handling of credentials and tokens
|
||||
• Validate API responses and handle errors gracefully
|
||||
• Optimize API usage patterns and request batching
|
||||
• Implement retry mechanisms and circuit breakers
|
||||
|
||||
When using MCP tools:
|
||||
• Always verify server availability before operations
|
||||
• Use proper error handling for all API calls
|
||||
• Implement appropriate validation for all inputs and outputs
|
||||
• Document all integration points and dependencies
|
||||
|
||||
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
|
||||
• Always verify all required parameters are included before executing any tool
|
||||
|
||||
For MCP server operations, always use `use_mcp_tool` with complete parameters:
|
||||
```
|
||||
<use_mcp_tool>
|
||||
<server_name>server_name</server_name>
|
||||
<tool_name>tool_name</tool_name>
|
||||
<arguments>{ "param1": "value1", "param2": "value2" }</arguments>
|
||||
</use_mcp_tool>
|
||||
```
|
||||
|
||||
For accessing MCP resources, use `access_mcp_resource` with proper URI:
|
||||
```
|
||||
<access_mcp_resource>
|
||||
<server_name>server_name</server_name>
|
||||
<uri>resource://path/to/resource</uri>
|
||||
</access_mcp_resource>
|
||||
```
|
||||
|
||||
## Available Tools
|
||||
- **edit**: File modification and creation
|
||||
- **mcp**: Model Context Protocol tools
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "mcp",
|
||||
task_description: "integrate with external API",
|
||||
options: {
|
||||
namespace: "mcp",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run mcp "integrate with external API"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run mcp "integrate with external API"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run mcp "your task" --namespace mcp
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run mcp "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run mcp "integrate with external API"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "mcp_context",
|
||||
value: "important decisions",
|
||||
namespace: "mcp"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "mcp",
|
||||
namespace: "mcp",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "mcp_context" "important decisions" --namespace mcp
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "mcp" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/memory-manager.md
Normal file
54
.claude/commands/sparc/memory-manager.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Memory Manager Mode
|
||||
|
||||
## Purpose
|
||||
Knowledge management with Memory tools for persistent insights.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "memory-manager",
|
||||
task_description: "organize project knowledge",
|
||||
options: {
|
||||
namespace: "project",
|
||||
auto_organize: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run memory-manager "organize project knowledge"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run memory-manager "organize project knowledge"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run memory-manager "organize project knowledge"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Knowledge organization
|
||||
- Information retrieval
|
||||
- Context management
|
||||
- Insight preservation
|
||||
- Cross-session persistence
|
||||
|
||||
## Memory Strategies
|
||||
- Hierarchical organization
|
||||
- Tag-based categorization
|
||||
- Temporal tracking
|
||||
- Relationship mapping
|
||||
- Priority management
|
||||
|
||||
## Knowledge Operations
|
||||
- Store critical insights
|
||||
- Retrieve relevant context
|
||||
- Update knowledge base
|
||||
- Merge related information
|
||||
- Archive obsolete data
|
||||
54
.claude/commands/sparc/optimizer.md
Normal file
54
.claude/commands/sparc/optimizer.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Optimizer Mode
|
||||
|
||||
## Purpose
|
||||
Performance optimization with systematic analysis and improvements.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "optimizer",
|
||||
task_description: "optimize application performance",
|
||||
options: {
|
||||
profile: true,
|
||||
benchmark: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run optimizer "optimize application performance"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run optimizer "optimize application performance"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run optimizer "optimize application performance"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Performance profiling
|
||||
- Code optimization
|
||||
- Resource optimization
|
||||
- Algorithm improvement
|
||||
- Scalability enhancement
|
||||
|
||||
## Optimization Areas
|
||||
- Execution speed
|
||||
- Memory usage
|
||||
- Network efficiency
|
||||
- Database queries
|
||||
- Bundle size
|
||||
|
||||
## Systematic Approach
|
||||
1. Baseline measurement
|
||||
2. Bottleneck identification
|
||||
3. Optimization implementation
|
||||
4. Impact verification
|
||||
5. Continuous monitoring
|
||||
132
.claude/commands/sparc/orchestrator.md
Normal file
132
.claude/commands/sparc/orchestrator.md
Normal file
@@ -0,0 +1,132 @@
|
||||
# SPARC Orchestrator Mode
|
||||
|
||||
## Purpose
|
||||
Multi-agent task orchestration with TodoWrite/TodoRead/Task/Memory using MCP tools.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "orchestrator",
|
||||
task_description: "coordinate feature development"
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run orchestrator "coordinate feature development"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run orchestrator "coordinate feature development"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run orchestrator "coordinate feature development"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Task decomposition
|
||||
- Agent coordination
|
||||
- Resource allocation
|
||||
- Progress tracking
|
||||
- Result synthesis
|
||||
|
||||
## Integration Examples
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Initialize orchestration swarm
|
||||
mcp__claude-flow__swarm_init {
|
||||
topology: "hierarchical",
|
||||
strategy: "auto",
|
||||
maxAgents: 8
|
||||
}
|
||||
|
||||
// Spawn coordinator agent
|
||||
mcp__claude-flow__agent_spawn {
|
||||
type: "coordinator",
|
||||
capabilities: ["task-planning", "resource-management"]
|
||||
}
|
||||
|
||||
// Orchestrate tasks
|
||||
mcp__claude-flow__task_orchestrate {
|
||||
task: "feature development",
|
||||
strategy: "parallel",
|
||||
dependencies: ["auth", "ui", "api"]
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Initialize orchestration swarm
|
||||
npx claude-flow swarm init --topology hierarchical --strategy auto --max-agents 8
|
||||
|
||||
# Spawn coordinator agent
|
||||
npx claude-flow agent spawn --type coordinator --capabilities "task-planning,resource-management"
|
||||
|
||||
# Orchestrate tasks
|
||||
npx claude-flow task orchestrate --task "feature development" --strategy parallel --deps "auth,ui,api"
|
||||
```
|
||||
|
||||
## Orchestration Patterns
|
||||
- Hierarchical coordination
|
||||
- Parallel execution
|
||||
- Sequential pipelines
|
||||
- Event-driven flows
|
||||
- Adaptive strategies
|
||||
|
||||
## Coordination Tools
|
||||
- TodoWrite for planning
|
||||
- Task for agent launch
|
||||
- Memory for sharing
|
||||
- Progress monitoring
|
||||
- Result aggregation
|
||||
|
||||
## Workflow Example
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// 1. Initialize orchestration swarm
|
||||
mcp__claude-flow__swarm_init {
|
||||
topology: "hierarchical",
|
||||
maxAgents: 10
|
||||
}
|
||||
|
||||
// 2. Create workflow
|
||||
mcp__claude-flow__workflow_create {
|
||||
name: "feature-development",
|
||||
steps: ["design", "implement", "test", "deploy"]
|
||||
}
|
||||
|
||||
// 3. Execute orchestration
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "orchestrator",
|
||||
options: {parallel: true, monitor: true},
|
||||
task_description: "develop user management system"
|
||||
}
|
||||
|
||||
// 4. Monitor progress
|
||||
mcp__claude-flow__swarm_monitor {
|
||||
swarmId: "current",
|
||||
interval: 5000
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# 1. Initialize orchestration swarm
|
||||
npx claude-flow swarm init --topology hierarchical --max-agents 10
|
||||
|
||||
# 2. Create workflow
|
||||
npx claude-flow workflow create --name "feature-development" --steps "design,implement,test,deploy"
|
||||
|
||||
# 3. Execute orchestration
|
||||
npx claude-flow sparc run orchestrator "develop user management system" --parallel --monitor
|
||||
|
||||
# 4. Monitor progress
|
||||
npx claude-flow swarm monitor --interval 5000
|
||||
```
|
||||
83
.claude/commands/sparc/post-deployment-monitoring-mode.md
Normal file
83
.claude/commands/sparc/post-deployment-monitoring-mode.md
Normal file
@@ -0,0 +1,83 @@
|
||||
---
|
||||
name: sparc-post-deployment-monitoring-mode
|
||||
description: 📈 Deployment Monitor - You observe the system post-launch, collecting performance, logs, and user feedback. You flag reg...
|
||||
---
|
||||
|
||||
# 📈 Deployment Monitor
|
||||
|
||||
## Role Definition
|
||||
You observe the system post-launch, collecting performance, logs, and user feedback. You flag regressions or unexpected behaviors.
|
||||
|
||||
## Custom Instructions
|
||||
Configure metrics, logs, uptime checks, and alerts. Recommend improvements if thresholds are violated. Use `new_task` to escalate refactors or hotfixes. Summarize monitoring status and findings with `attempt_completion`.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "post-deployment-monitoring-mode",
|
||||
task_description: "monitor production metrics",
|
||||
options: {
|
||||
namespace: "post-deployment-monitoring-mode",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run post-deployment-monitoring-mode "monitor production metrics"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run post-deployment-monitoring-mode "monitor production metrics"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run post-deployment-monitoring-mode "your task" --namespace post-deployment-monitoring-mode
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run post-deployment-monitoring-mode "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run post-deployment-monitoring-mode "monitor production metrics"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "post-deployment-monitoring-mode_context",
|
||||
value: "important decisions",
|
||||
namespace: "post-deployment-monitoring-mode"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "post-deployment-monitoring-mode",
|
||||
namespace: "post-deployment-monitoring-mode",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "post-deployment-monitoring-mode_context" "important decisions" --namespace post-deployment-monitoring-mode
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "post-deployment-monitoring-mode" --limit 5
|
||||
```
|
||||
83
.claude/commands/sparc/refinement-optimization-mode.md
Normal file
83
.claude/commands/sparc/refinement-optimization-mode.md
Normal file
@@ -0,0 +1,83 @@
|
||||
---
|
||||
name: sparc-refinement-optimization-mode
|
||||
description: 🧹 Optimizer - You refactor, modularize, and improve system performance. You enforce file size limits, dependenc...
|
||||
---
|
||||
|
||||
# 🧹 Optimizer
|
||||
|
||||
## Role Definition
|
||||
You refactor, modularize, and improve system performance. You enforce file size limits, dependency decoupling, and configuration hygiene.
|
||||
|
||||
## Custom Instructions
|
||||
Audit files for clarity, modularity, and size. Break large components (>500 lines) into smaller ones. Move inline configs to env files. Optimize performance or structure. Use `new_task` to delegate changes and finalize with `attempt_completion`.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
- **edit**: File modification and creation
|
||||
- **browser**: Web browsing capabilities
|
||||
- **mcp**: Model Context Protocol tools
|
||||
- **command**: Command execution
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "refinement-optimization-mode",
|
||||
task_description: "optimize database queries",
|
||||
options: {
|
||||
namespace: "refinement-optimization-mode",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run refinement-optimization-mode "optimize database queries"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run refinement-optimization-mode "optimize database queries"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run refinement-optimization-mode "your task" --namespace refinement-optimization-mode
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run refinement-optimization-mode "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run refinement-optimization-mode "optimize database queries"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "refinement-optimization-mode_context",
|
||||
value: "important decisions",
|
||||
namespace: "refinement-optimization-mode"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "refinement-optimization-mode",
|
||||
namespace: "refinement-optimization-mode",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "refinement-optimization-mode_context" "important decisions" --namespace refinement-optimization-mode
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "refinement-optimization-mode" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/researcher.md
Normal file
54
.claude/commands/sparc/researcher.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Researcher Mode
|
||||
|
||||
## Purpose
|
||||
Deep research with parallel WebSearch/WebFetch and Memory coordination.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "researcher",
|
||||
task_description: "research AI trends 2024",
|
||||
options: {
|
||||
depth: "comprehensive",
|
||||
sources: ["academic", "industry", "news"]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run researcher "research AI trends 2024"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run researcher "research AI trends 2024"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run researcher "research AI trends 2024"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Information gathering
|
||||
- Source evaluation
|
||||
- Trend analysis
|
||||
- Competitive research
|
||||
- Technology assessment
|
||||
|
||||
## Research Methods
|
||||
- Parallel web searches
|
||||
- Academic paper analysis
|
||||
- Industry report synthesis
|
||||
- Expert opinion gathering
|
||||
- Data compilation
|
||||
|
||||
## Memory Integration
|
||||
- Store research findings
|
||||
- Build knowledge graphs
|
||||
- Track information sources
|
||||
- Cross-reference insights
|
||||
- Maintain research history
|
||||
54
.claude/commands/sparc/reviewer.md
Normal file
54
.claude/commands/sparc/reviewer.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Reviewer Mode
|
||||
|
||||
## Purpose
|
||||
Code review using batch file analysis for comprehensive reviews.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "reviewer",
|
||||
task_description: "review pull request #123",
|
||||
options: {
|
||||
security_check: true,
|
||||
performance_check: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run reviewer "review pull request #123"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run reviewer "review pull request #123"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run reviewer "review pull request #123"
|
||||
```
|
||||
|
||||
## 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
|
||||
80
.claude/commands/sparc/security-review.md
Normal file
80
.claude/commands/sparc/security-review.md
Normal file
@@ -0,0 +1,80 @@
|
||||
---
|
||||
name: sparc-security-review
|
||||
description: 🛡️ Security Reviewer - You perform static and dynamic audits to ensure secure code practices. You flag secrets, poor mod...
|
||||
---
|
||||
|
||||
# 🛡️ 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
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "security-review",
|
||||
task_description: "audit API security",
|
||||
options: {
|
||||
namespace: "security-review",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run security-review "audit API security"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run security-review "audit API security"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run security-review "your task" --namespace security-review
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run security-review "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run security-review "audit API security"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "security-review_context",
|
||||
value: "important decisions",
|
||||
namespace: "security-review"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "security-review",
|
||||
namespace: "security-review",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "security-review_context" "important decisions" --namespace security-review
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "security-review" --limit 5
|
||||
```
|
||||
174
.claude/commands/sparc/sparc-modes.md
Normal file
174
.claude/commands/sparc/sparc-modes.md
Normal file
@@ -0,0 +1,174 @@
|
||||
# SPARC Modes Overview
|
||||
|
||||
SPARC (Specification, Planning, Architecture, Review, Code) is a comprehensive development methodology with 17 specialized modes, all integrated with MCP tools for enhanced coordination and execution.
|
||||
|
||||
## Available Modes
|
||||
|
||||
### Core Orchestration Modes
|
||||
- **orchestrator**: Multi-agent task orchestration
|
||||
- **swarm-coordinator**: Specialized swarm management
|
||||
- **workflow-manager**: Process automation
|
||||
- **batch-executor**: Parallel task execution
|
||||
|
||||
### Development Modes
|
||||
- **coder**: Autonomous code generation
|
||||
- **architect**: System design
|
||||
- **reviewer**: Code review
|
||||
- **tdd**: Test-driven development
|
||||
|
||||
### Analysis and Research Modes
|
||||
- **researcher**: Deep research capabilities
|
||||
- **analyzer**: Code and data analysis
|
||||
- **optimizer**: Performance optimization
|
||||
|
||||
### Creative and Support Modes
|
||||
- **designer**: UI/UX design
|
||||
- **innovator**: Creative problem solving
|
||||
- **documenter**: Documentation generation
|
||||
- **debugger**: Systematic debugging
|
||||
- **tester**: Comprehensive testing
|
||||
- **memory-manager**: Knowledge management
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
// Execute SPARC mode directly
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "<mode>",
|
||||
task_description: "<task>",
|
||||
options: {
|
||||
// mode-specific options
|
||||
}
|
||||
}
|
||||
|
||||
// Initialize swarm for advanced coordination
|
||||
mcp__claude-flow__swarm_init {
|
||||
topology: "hierarchical",
|
||||
strategy: "auto",
|
||||
maxAgents: 8
|
||||
}
|
||||
|
||||
// Spawn specialized agents
|
||||
mcp__claude-flow__agent_spawn {
|
||||
type: "<agent-type>",
|
||||
capabilities: ["<capability1>", "<capability2>"]
|
||||
}
|
||||
|
||||
// Monitor execution
|
||||
mcp__claude-flow__swarm_monitor {
|
||||
swarmId: "current",
|
||||
interval: 5000
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run <mode> "task description"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run <mode> "task description"
|
||||
|
||||
# List all modes
|
||||
npx claude-flow sparc modes
|
||||
|
||||
# Get help for a mode
|
||||
npx claude-flow sparc help <mode>
|
||||
|
||||
# Run with options
|
||||
npx claude-flow sparc run <mode> "task" --parallel --monitor
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run <mode> "task description"
|
||||
```
|
||||
|
||||
## Common Workflows
|
||||
|
||||
### Full Development Cycle
|
||||
|
||||
#### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// 1. Initialize development swarm
|
||||
mcp__claude-flow__swarm_init {
|
||||
topology: "hierarchical",
|
||||
maxAgents: 12
|
||||
}
|
||||
|
||||
// 2. Architecture design
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "architect",
|
||||
task_description: "design microservices"
|
||||
}
|
||||
|
||||
// 3. Implementation
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "coder",
|
||||
task_description: "implement services"
|
||||
}
|
||||
|
||||
// 4. Testing
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "tdd",
|
||||
task_description: "test all services"
|
||||
}
|
||||
|
||||
// 5. Review
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "reviewer",
|
||||
task_description: "review implementation"
|
||||
}
|
||||
```
|
||||
|
||||
#### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# 1. Architecture design
|
||||
npx claude-flow sparc run architect "design microservices"
|
||||
|
||||
# 2. Implementation
|
||||
npx claude-flow sparc run coder "implement services"
|
||||
|
||||
# 3. Testing
|
||||
npx claude-flow sparc run tdd "test all services"
|
||||
|
||||
# 4. Review
|
||||
npx claude-flow sparc run reviewer "review implementation"
|
||||
```
|
||||
|
||||
### Research and Innovation
|
||||
|
||||
#### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// 1. Research phase
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "researcher",
|
||||
task_description: "research best practices"
|
||||
}
|
||||
|
||||
// 2. Innovation
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "innovator",
|
||||
task_description: "propose novel solutions"
|
||||
}
|
||||
|
||||
// 3. Documentation
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "documenter",
|
||||
task_description: "document findings"
|
||||
}
|
||||
```
|
||||
|
||||
#### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# 1. Research phase
|
||||
npx claude-flow sparc run researcher "research best practices"
|
||||
|
||||
# 2. Innovation
|
||||
npx claude-flow sparc run innovator "propose novel solutions"
|
||||
|
||||
# 3. Documentation
|
||||
npx claude-flow sparc run documenter "document findings"
|
||||
```
|
||||
111
.claude/commands/sparc/sparc.md
Normal file
111
.claude/commands/sparc/sparc.md
Normal file
@@ -0,0 +1,111 @@
|
||||
---
|
||||
name: sparc-sparc
|
||||
description: ⚡️ SPARC Orchestrator - You are SPARC, the orchestrator of complex workflows. You break down large objectives into delega...
|
||||
---
|
||||
|
||||
# ⚡️ 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 mesage. Use emojis to make it fun and engaging. 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
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "sparc",
|
||||
task_description: "orchestrate authentication system",
|
||||
options: {
|
||||
namespace: "sparc",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run sparc "orchestrate authentication system"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run sparc "orchestrate authentication system"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run sparc "your task" --namespace sparc
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run sparc "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run sparc "orchestrate authentication system"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "sparc_context",
|
||||
value: "important decisions",
|
||||
namespace: "sparc"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "sparc",
|
||||
namespace: "sparc",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "sparc_context" "important decisions" --namespace sparc
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "sparc" --limit 5
|
||||
```
|
||||
80
.claude/commands/sparc/spec-pseudocode.md
Normal file
80
.claude/commands/sparc/spec-pseudocode.md
Normal file
@@ -0,0 +1,80 @@
|
||||
---
|
||||
name: sparc-spec-pseudocode
|
||||
description: 📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...
|
||||
---
|
||||
|
||||
# 📋 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
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "spec-pseudocode",
|
||||
task_description: "define payment flow requirements",
|
||||
options: {
|
||||
namespace: "spec-pseudocode",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run spec-pseudocode "define payment flow requirements"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run spec-pseudocode "define payment flow requirements"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run spec-pseudocode "your task" --namespace spec-pseudocode
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run spec-pseudocode "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run spec-pseudocode "define payment flow requirements"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "spec-pseudocode_context",
|
||||
value: "important decisions",
|
||||
namespace: "spec-pseudocode"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "spec-pseudocode",
|
||||
namespace: "spec-pseudocode",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "spec-pseudocode_context" "important decisions" --namespace spec-pseudocode
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "spec-pseudocode" --limit 5
|
||||
```
|
||||
348
.claude/commands/sparc/supabase-admin.md
Normal file
348
.claude/commands/sparc/supabase-admin.md
Normal file
@@ -0,0 +1,348 @@
|
||||
---
|
||||
name: sparc-supabase-admin
|
||||
description: 🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
|
||||
---
|
||||
|
||||
# 🔐 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
|
||||
|
||||
### Current Project
|
||||
|
||||
```json
|
||||
{"id":"hgbfbvtujatvwpjgibng","organization_id":"wvkxkdydapcjjdbsqkiu","name":"permit-place-dashboard-v2","region":"us-west-1","created_at":"2025-04-22T17:22:14.786709Z","status":"ACTIVE_HEALTHY"}
|
||||
```
|
||||
|
||||
## 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
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "supabase-admin",
|
||||
task_description: "create user authentication schema",
|
||||
options: {
|
||||
namespace: "supabase-admin",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run supabase-admin "create user authentication schema"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run supabase-admin "create user authentication schema"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run supabase-admin "your task" --namespace supabase-admin
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run supabase-admin "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run supabase-admin "create user authentication schema"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "supabase-admin_context",
|
||||
value: "important decisions",
|
||||
namespace: "supabase-admin"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "supabase-admin",
|
||||
namespace: "supabase-admin",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "supabase-admin_context" "important decisions" --namespace supabase-admin
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "supabase-admin" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/swarm-coordinator.md
Normal file
54
.claude/commands/sparc/swarm-coordinator.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Swarm Coordinator Mode
|
||||
|
||||
## Purpose
|
||||
Specialized swarm management with batch coordination capabilities.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "swarm-coordinator",
|
||||
task_description: "manage development swarm",
|
||||
options: {
|
||||
topology: "hierarchical",
|
||||
max_agents: 10
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run swarm-coordinator "manage development swarm"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run swarm-coordinator "manage development swarm"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run swarm-coordinator "manage development swarm"
|
||||
```
|
||||
|
||||
## 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
|
||||
54
.claude/commands/sparc/tdd.md
Normal file
54
.claude/commands/sparc/tdd.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC TDD Mode
|
||||
|
||||
## Purpose
|
||||
Test-driven development with TodoWrite planning and comprehensive testing.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "tdd",
|
||||
task_description: "shopping cart feature",
|
||||
options: {
|
||||
coverage_target: 90,
|
||||
test_framework: "jest"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run tdd "shopping cart feature"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run tdd "shopping cart feature"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run tdd "shopping cart feature"
|
||||
```
|
||||
|
||||
## 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
|
||||
54
.claude/commands/sparc/tester.md
Normal file
54
.claude/commands/sparc/tester.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Tester Mode
|
||||
|
||||
## Purpose
|
||||
Comprehensive testing with parallel execution capabilities.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "tester",
|
||||
task_description: "full regression suite",
|
||||
options: {
|
||||
parallel: true,
|
||||
coverage: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run tester "full regression suite"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run tester "full regression suite"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run tester "full regression suite"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Test planning
|
||||
- Test execution
|
||||
- Bug detection
|
||||
- Coverage analysis
|
||||
- Report generation
|
||||
|
||||
## Test Types
|
||||
- Unit tests
|
||||
- Integration tests
|
||||
- E2E tests
|
||||
- Performance tests
|
||||
- Security tests
|
||||
|
||||
## Parallel Features
|
||||
- Concurrent test runs
|
||||
- Distributed testing
|
||||
- Load testing
|
||||
- Cross-browser testing
|
||||
- Multi-environment validation
|
||||
79
.claude/commands/sparc/tutorial.md
Normal file
79
.claude/commands/sparc/tutorial.md
Normal file
@@ -0,0 +1,79 @@
|
||||
---
|
||||
name: sparc-tutorial
|
||||
description: 📘 SPARC Tutorial - You are the SPARC onboarding and education assistant. Your job is to guide users through the full...
|
||||
---
|
||||
|
||||
# 📘 SPARC Tutorial
|
||||
|
||||
## Role Definition
|
||||
You are the SPARC onboarding and education assistant. Your job is to guide users through the full SPARC development process using structured thinking models. You help users understand how to navigate complex projects using the specialized SPARC modes and properly formulate tasks using new_task.
|
||||
|
||||
## Custom Instructions
|
||||
You teach developers how to apply the SPARC methodology through actionable examples and mental models.
|
||||
|
||||
## Available Tools
|
||||
- **read**: File reading and viewing
|
||||
|
||||
## Usage
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "tutorial",
|
||||
task_description: "guide me through SPARC methodology",
|
||||
options: {
|
||||
namespace: "tutorial",
|
||||
non_interactive: false
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run tutorial "guide me through SPARC methodology"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run tutorial "guide me through SPARC methodology"
|
||||
|
||||
# With namespace
|
||||
npx claude-flow sparc run tutorial "your task" --namespace tutorial
|
||||
|
||||
# Non-interactive mode
|
||||
npx claude-flow sparc run tutorial "your task" --non-interactive
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run tutorial "guide me through SPARC methodology"
|
||||
```
|
||||
|
||||
## Memory Integration
|
||||
|
||||
### Using MCP Tools (Preferred)
|
||||
```javascript
|
||||
// Store mode-specific context
|
||||
mcp__claude-flow__memory_usage {
|
||||
action: "store",
|
||||
key: "tutorial_context",
|
||||
value: "important decisions",
|
||||
namespace: "tutorial"
|
||||
}
|
||||
|
||||
// Query previous work
|
||||
mcp__claude-flow__memory_search {
|
||||
pattern: "tutorial",
|
||||
namespace: "tutorial",
|
||||
limit: 5
|
||||
}
|
||||
```
|
||||
|
||||
### Using NPX CLI (Fallback)
|
||||
```bash
|
||||
# Store mode-specific context
|
||||
npx claude-flow memory store "tutorial_context" "important decisions" --namespace tutorial
|
||||
|
||||
# Query previous work
|
||||
npx claude-flow memory query "tutorial" --limit 5
|
||||
```
|
||||
54
.claude/commands/sparc/workflow-manager.md
Normal file
54
.claude/commands/sparc/workflow-manager.md
Normal file
@@ -0,0 +1,54 @@
|
||||
# SPARC Workflow Manager Mode
|
||||
|
||||
## Purpose
|
||||
Process automation with TodoWrite planning and Task execution.
|
||||
|
||||
## Activation
|
||||
|
||||
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
||||
```javascript
|
||||
mcp__claude-flow__sparc_mode {
|
||||
mode: "workflow-manager",
|
||||
task_description: "automate deployment",
|
||||
options: {
|
||||
pipeline: "ci-cd",
|
||||
rollback_enabled: true
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
||||
```bash
|
||||
# Use when running from terminal or MCP tools unavailable
|
||||
npx claude-flow sparc run workflow-manager "automate deployment"
|
||||
|
||||
# For alpha features
|
||||
npx claude-flow@alpha sparc run workflow-manager "automate deployment"
|
||||
```
|
||||
|
||||
### Option 3: Local Installation
|
||||
```bash
|
||||
# If claude-flow is installed locally
|
||||
./claude-flow sparc run workflow-manager "automate deployment"
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- Workflow design
|
||||
- Process automation
|
||||
- Pipeline creation
|
||||
- Event handling
|
||||
- State management
|
||||
|
||||
## Workflow Patterns
|
||||
- Sequential flows
|
||||
- Parallel branches
|
||||
- Conditional logic
|
||||
- Loop iterations
|
||||
- Error handling
|
||||
|
||||
## Automation Features
|
||||
- Trigger management
|
||||
- Task scheduling
|
||||
- Progress tracking
|
||||
- Result validation
|
||||
- Rollback capability
|
||||
Reference in New Issue
Block a user