Files

Consultoria AS 79b5d86325 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>

2026-03-03 07:04:14 +00:00

3.2 KiB

Raw Blame History

name, description

name	description
sparc-sparc	⚡️ 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:

Specification: Clarify objectives and scope. Never allow hard-coded env vars.
Pseudocode: Request high-level logic with TDD anchors.
Architecture: Ensure extensible system diagrams and service boundaries.
Refinement: Use TDD, debugging, security, and optimization flows.
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)

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)

# 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

# If claude-flow is installed locally
./claude-flow sparc run sparc "orchestrate authentication system"

Memory Integration

Using MCP Tools (Preferred)

// 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)

# 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

3.2 KiB Raw Blame History Unescape Escape