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:
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
|
||||
Reference in New Issue
Block a user