oden-forge 2.0.2 → 2.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/CLAUDE.md +1 -1
- package/.claude/commands/oden/architect.md +63 -8
- package/.claude/commands/oden/debug.md +502 -133
- package/.claude/commands/oden/epic.md +52 -0
- package/.claude/commands/oden/init.md +51 -0
- package/.claude/commands/oden/work.md +154 -0
- package/README.md +12 -42
- package/package.json +1 -1
- package/.claude/commands/oden/checklist.md +0 -199
- package/.claude/commands/oden/daily.md +0 -223
- package/.claude/commands/oden/git.md +0 -259
- package/.claude/commands/oden/init-agents.md +0 -268
- package/.claude/commands/oden/init-mcp.md +0 -460
- package/.claude/commands/oden/research.md +0 -207
- package/.claude/commands/oden/review.md +0 -146
- package/.claude/commands/oden/spec.md +0 -539
- package/.claude/commands/oden/tasks.md +0 -156
- package/.claude/commands/oden/test.md +0 -200
|
@@ -1,268 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
allowed-tools: Bash, Read, Write, LS, Glob
|
|
3
|
-
description: Instalar agentes útiles para desarrollo de aplicaciones
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Oden Forge - Init Agents
|
|
7
|
-
|
|
8
|
-
Instala una colección curada de agentes especializados para desarrollo de aplicaciones.
|
|
9
|
-
|
|
10
|
-
## Usage
|
|
11
|
-
|
|
12
|
-
```
|
|
13
|
-
/oden:init-agents [category]
|
|
14
|
-
```
|
|
15
|
-
|
|
16
|
-
Categories:
|
|
17
|
-
- (vacío) - Instalar todos los agentes recomendados
|
|
18
|
-
- `core` - Solo agentes esenciales
|
|
19
|
-
- `frontend` - Agentes de frontend
|
|
20
|
-
- `backend` - Agentes de backend
|
|
21
|
-
- `mobile` - Agentes de mobile
|
|
22
|
-
- `devops` - Agentes de DevOps
|
|
23
|
-
- `data` - Agentes de datos
|
|
24
|
-
|
|
25
|
-
## Agentes Disponibles
|
|
26
|
-
|
|
27
|
-
### Core (Esenciales) - `core`
|
|
28
|
-
|
|
29
|
-
Agentes fundamentales para cualquier proyecto:
|
|
30
|
-
|
|
31
|
-
| Agente | Descripción | Uso |
|
|
32
|
-
|--------|-------------|-----|
|
|
33
|
-
| `fullstack-developer` | Desarrollo end-to-end | Implementación general |
|
|
34
|
-
| `code-reviewer` | Code review | Revisar PRs y código |
|
|
35
|
-
| `debugger` | Debugging | Resolver errores |
|
|
36
|
-
| `test-engineer` | Testing | Estrategia y tests |
|
|
37
|
-
| `code-analyzer` | Análisis de código | Buscar bugs potenciales |
|
|
38
|
-
| `technical-writer` | Documentación | Escribir docs |
|
|
39
|
-
| `git-flow-manager` | Git workflow | Branches y PRs |
|
|
40
|
-
|
|
41
|
-
### Frontend - `frontend`
|
|
42
|
-
|
|
43
|
-
| Agente | Descripción | Uso |
|
|
44
|
-
|--------|-------------|-----|
|
|
45
|
-
| `frontend-developer` | React/Vue/Svelte | UI components |
|
|
46
|
-
| `ui-ux-designer` | Diseño de interfaces | UX/UI |
|
|
47
|
-
| `javascript-pro` | JavaScript avanzado | ES6+, async |
|
|
48
|
-
| `graphql-architect` | GraphQL | APIs GraphQL |
|
|
49
|
-
|
|
50
|
-
### Backend - `backend`
|
|
51
|
-
|
|
52
|
-
| Agente | Descripción | Uso |
|
|
53
|
-
|--------|-------------|-----|
|
|
54
|
-
| `backend-architect` | Arquitectura backend | APIs, servicios |
|
|
55
|
-
| `database-architect` | Diseño de BD | Schemas, queries |
|
|
56
|
-
| `database-optimization` | Optimización BD | Performance |
|
|
57
|
-
| `python-pro` | Python | FastAPI, Django |
|
|
58
|
-
| `php-pro` | PHP | Laravel, etc. |
|
|
59
|
-
|
|
60
|
-
### Mobile - `mobile`
|
|
61
|
-
|
|
62
|
-
| Agente | Descripción | Uso |
|
|
63
|
-
|--------|-------------|-----|
|
|
64
|
-
| `mobile-developer` | Cross-platform | React Native, Flutter |
|
|
65
|
-
| `ios-developer` | iOS nativo | Swift, SwiftUI |
|
|
66
|
-
|
|
67
|
-
### DevOps - `devops`
|
|
68
|
-
|
|
69
|
-
| Agente | Descripción | Uso |
|
|
70
|
-
|--------|-------------|-----|
|
|
71
|
-
| `devops-engineer` | CI/CD, infra | Pipelines |
|
|
72
|
-
| `deployment-engineer` | Deployments | Releases |
|
|
73
|
-
| `performance-engineer` | Performance | Optimización |
|
|
74
|
-
|
|
75
|
-
### Data - `data`
|
|
76
|
-
|
|
77
|
-
| Agente | Descripción | Uso |
|
|
78
|
-
|--------|-------------|-----|
|
|
79
|
-
| `data-engineer` | Data pipelines | ETL |
|
|
80
|
-
| `data-analyst` | Análisis | Métricas |
|
|
81
|
-
| `data-scientist` | ML/Stats | Modelos |
|
|
82
|
-
|
|
83
|
-
### Especialistas
|
|
84
|
-
|
|
85
|
-
| Agente | Descripción | Uso |
|
|
86
|
-
|--------|-------------|-----|
|
|
87
|
-
| `ai-engineer` | LLM/RAG | Integrar IA |
|
|
88
|
-
| `mcp-expert` | MCP servers | Integraciones |
|
|
89
|
-
| `prompt-engineer` | Prompts | Optimizar prompts |
|
|
90
|
-
| `search-specialist` | Búsqueda web | Investigación |
|
|
91
|
-
| `technical-researcher` | Research técnico | Evaluar opciones |
|
|
92
|
-
| `error-detective` | Logs/errores | Debug avanzado |
|
|
93
|
-
| `penetration-tester` | Seguridad | Auditorías |
|
|
94
|
-
|
|
95
|
-
### Utilidades
|
|
96
|
-
|
|
97
|
-
| Agente | Descripción | Uso |
|
|
98
|
-
|--------|-------------|-----|
|
|
99
|
-
| `parallel-worker` | Trabajo paralelo | Multi-tareas |
|
|
100
|
-
| `file-analyzer` | Análisis archivos | Logs, outputs |
|
|
101
|
-
| `test-runner` | Ejecutar tests | CI/tests |
|
|
102
|
-
| `context-manager` | Contexto | Sesiones largas |
|
|
103
|
-
|
|
104
|
-
---
|
|
105
|
-
|
|
106
|
-
## Instrucciones de Instalación
|
|
107
|
-
|
|
108
|
-
### Verificar directorio de agentes
|
|
109
|
-
|
|
110
|
-
```bash
|
|
111
|
-
# Verificar que existe el directorio
|
|
112
|
-
mkdir -p ~/.claude/agents
|
|
113
|
-
|
|
114
|
-
# Listar agentes actuales
|
|
115
|
-
ls ~/.claude/agents/*.md 2>/dev/null | wc -l
|
|
116
|
-
```
|
|
117
|
-
|
|
118
|
-
### Descargar Agentes
|
|
119
|
-
|
|
120
|
-
Los agentes se descargan desde el repositorio de Oden Forge:
|
|
121
|
-
|
|
122
|
-
```bash
|
|
123
|
-
ODEN_REPO="https://raw.githubusercontent.com/tu-usuario/oden-forge/main"
|
|
124
|
-
|
|
125
|
-
# Core agents
|
|
126
|
-
for agent in fullstack-developer code-reviewer debugger test-engineer code-analyzer technical-writer git-flow-manager; do
|
|
127
|
-
curl -sL "$ODEN_REPO/agents/$agent.md" -o ~/.claude/agents/$agent.md
|
|
128
|
-
done
|
|
129
|
-
```
|
|
130
|
-
|
|
131
|
-
### Alternativamente: Copiar desde local
|
|
132
|
-
|
|
133
|
-
Si tienes Oden Forge clonado:
|
|
134
|
-
|
|
135
|
-
```bash
|
|
136
|
-
cp /path/to/oden-forge/.claude/agents/*.md ~/.claude/agents/
|
|
137
|
-
```
|
|
138
|
-
|
|
139
|
-
---
|
|
140
|
-
|
|
141
|
-
## Proceso de Instalación
|
|
142
|
-
|
|
143
|
-
### Paso 1: Detectar agentes existentes
|
|
144
|
-
|
|
145
|
-
```bash
|
|
146
|
-
echo "=== Agentes actuales ==="
|
|
147
|
-
ls ~/.claude/agents/*.md 2>/dev/null | while read f; do
|
|
148
|
-
basename "$f" .md
|
|
149
|
-
done
|
|
150
|
-
```
|
|
151
|
-
|
|
152
|
-
### Paso 2: Selección por categoría
|
|
153
|
-
|
|
154
|
-
Si el usuario especificó categoría:
|
|
155
|
-
- `core`: Instalar solo los 7 agentes esenciales
|
|
156
|
-
- `frontend`: Core + 4 agentes de frontend
|
|
157
|
-
- `backend`: Core + 5 agentes de backend
|
|
158
|
-
- `mobile`: Core + 2 agentes de mobile
|
|
159
|
-
- `devops`: Core + 3 agentes de devops
|
|
160
|
-
- `data`: Core + 3 agentes de data
|
|
161
|
-
- (vacío): Todos los agentes recomendados
|
|
162
|
-
|
|
163
|
-
### Paso 3: Copiar agentes
|
|
164
|
-
|
|
165
|
-
Los agentes incluidos en Oden Forge están en:
|
|
166
|
-
```
|
|
167
|
-
oden-forge/.claude/agents-library/
|
|
168
|
-
```
|
|
169
|
-
|
|
170
|
-
Copiar a:
|
|
171
|
-
```
|
|
172
|
-
~/.claude/agents/
|
|
173
|
-
```
|
|
174
|
-
|
|
175
|
-
### Paso 4: Verificar instalación
|
|
176
|
-
|
|
177
|
-
```bash
|
|
178
|
-
echo "=== Agentes instalados ==="
|
|
179
|
-
ls ~/.claude/agents/*.md | wc -l
|
|
180
|
-
echo "agentes instalados"
|
|
181
|
-
```
|
|
182
|
-
|
|
183
|
-
---
|
|
184
|
-
|
|
185
|
-
## Output
|
|
186
|
-
|
|
187
|
-
```
|
|
188
|
-
╔══════════════════════════════════════════════════════════════╗
|
|
189
|
-
║ ODEN FORGE - AGENTS INSTALLED ║
|
|
190
|
-
╠══════════════════════════════════════════════════════════════╣
|
|
191
|
-
║ ║
|
|
192
|
-
║ ✅ Instalados: {N} agentes ║
|
|
193
|
-
║ ║
|
|
194
|
-
║ CORE: ║
|
|
195
|
-
║ ├─ fullstack-developer ║
|
|
196
|
-
║ ├─ code-reviewer ║
|
|
197
|
-
║ ├─ debugger ║
|
|
198
|
-
║ ├─ test-engineer ║
|
|
199
|
-
║ ├─ code-analyzer ║
|
|
200
|
-
║ ├─ technical-writer ║
|
|
201
|
-
║ └─ git-flow-manager ║
|
|
202
|
-
║ ║
|
|
203
|
-
║ {CATEGORY}: ║
|
|
204
|
-
║ ├─ {agent1} ║
|
|
205
|
-
║ └─ {agent2} ║
|
|
206
|
-
║ ║
|
|
207
|
-
╠══════════════════════════════════════════════════════════════╣
|
|
208
|
-
║ ║
|
|
209
|
-
║ USO: ║
|
|
210
|
-
║ Los agentes están disponibles vía /oden:dev ║
|
|
211
|
-
║ ║
|
|
212
|
-
║ Ejemplos: ║
|
|
213
|
-
║ /oden:dev fullstack → Desarrollo end-to-end ║
|
|
214
|
-
║ /oden:dev debug → Debugging ║
|
|
215
|
-
║ /oden:dev test → Testing ║
|
|
216
|
-
║ /oden:dev review → Code review ║
|
|
217
|
-
║ ║
|
|
218
|
-
╚══════════════════════════════════════════════════════════════╝
|
|
219
|
-
```
|
|
220
|
-
|
|
221
|
-
---
|
|
222
|
-
|
|
223
|
-
## Agentes Ya Instalados
|
|
224
|
-
|
|
225
|
-
Si el usuario ya tiene agentes (como los de CCPM), este comando:
|
|
226
|
-
1. Lista los existentes
|
|
227
|
-
2. Pregunta si quiere agregar los nuevos
|
|
228
|
-
3. No sobrescribe sin confirmación
|
|
229
|
-
|
|
230
|
-
---
|
|
231
|
-
|
|
232
|
-
## Crear Agentes Personalizados
|
|
233
|
-
|
|
234
|
-
Para crear un agente personalizado:
|
|
235
|
-
|
|
236
|
-
```markdown
|
|
237
|
-
# ~/.claude/agents/mi-agente.md
|
|
238
|
-
|
|
239
|
-
---
|
|
240
|
-
name: mi-agente
|
|
241
|
-
description: Descripción del agente
|
|
242
|
-
model: sonnet
|
|
243
|
-
tools: Read, Write, Edit, Bash
|
|
244
|
-
---
|
|
245
|
-
|
|
246
|
-
# Mi Agente
|
|
247
|
-
|
|
248
|
-
## Rol
|
|
249
|
-
{Descripción del rol}
|
|
250
|
-
|
|
251
|
-
## Responsabilidades
|
|
252
|
-
1. {responsabilidad 1}
|
|
253
|
-
2. {responsabilidad 2}
|
|
254
|
-
|
|
255
|
-
## Proceso
|
|
256
|
-
{Cómo trabaja}
|
|
257
|
-
|
|
258
|
-
## Output
|
|
259
|
-
{Qué produce}
|
|
260
|
-
```
|
|
261
|
-
|
|
262
|
-
---
|
|
263
|
-
|
|
264
|
-
## Notas
|
|
265
|
-
|
|
266
|
-
- Los agentes se invocan con `Task` tool y `subagent_type`
|
|
267
|
-
- Requieren Claude Code con soporte de agentes
|
|
268
|
-
- Los agentes son archivos `.md` en `~/.claude/agents/`
|
|
@@ -1,460 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
allowed-tools: Bash, Read, Write, LS
|
|
3
|
-
description: Instalar MCPs recomendados para desarrollo
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Oden Forge - Init MCP
|
|
7
|
-
|
|
8
|
-
Instala y configura MCPs (Model Context Protocol servers) recomendados para desarrollo.
|
|
9
|
-
|
|
10
|
-
## Usage
|
|
11
|
-
|
|
12
|
-
```
|
|
13
|
-
/oden:init-mcp [category]
|
|
14
|
-
```
|
|
15
|
-
|
|
16
|
-
Categories:
|
|
17
|
-
- (vacío) - Mostrar todos los MCPs disponibles
|
|
18
|
-
- `essential` - MCPs esenciales para cualquier proyecto
|
|
19
|
-
- `design` - MCPs de diseño (Figma)
|
|
20
|
-
- `backend` - MCPs de backend (Supabase)
|
|
21
|
-
- `productivity` - MCPs de productividad (Notion)
|
|
22
|
-
- `devops` - MCPs de DevOps (Vercel)
|
|
23
|
-
- `testing` - MCPs de testing (Playwright, Chrome DevTools)
|
|
24
|
-
- `mobile` - MCPs de mobile (iOS Simulator)
|
|
25
|
-
|
|
26
|
-
## MCPs Disponibles
|
|
27
|
-
|
|
28
|
-
### Essential - `essential`
|
|
29
|
-
|
|
30
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
31
|
-
|-----|------|-------------|----------|
|
|
32
|
-
| `context7` | HTTP | Documentación actualizada de librerías | API Key (gratis) |
|
|
33
|
-
|
|
34
|
-
### Design - `design`
|
|
35
|
-
|
|
36
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
37
|
-
|-----|------|-------------|----------|
|
|
38
|
-
| `figma` | HTTP | Acceso a diseños de Figma | Cuenta Figma |
|
|
39
|
-
|
|
40
|
-
### Backend - `backend`
|
|
41
|
-
|
|
42
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
43
|
-
|-----|------|-------------|----------|
|
|
44
|
-
| `supabase` | NPX | Gestión de Supabase DB | Access Token + Project Ref |
|
|
45
|
-
|
|
46
|
-
### Productivity - `productivity`
|
|
47
|
-
|
|
48
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
49
|
-
|-----|------|-------------|----------|
|
|
50
|
-
| `notion` | HTTP | Acceso a Notion | Cuenta Notion |
|
|
51
|
-
|
|
52
|
-
### DevOps - `devops`
|
|
53
|
-
|
|
54
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
55
|
-
|-----|------|-------------|----------|
|
|
56
|
-
| `vercel` | HTTP | Deploy y gestión Vercel | Cuenta Vercel |
|
|
57
|
-
|
|
58
|
-
### Testing - `testing`
|
|
59
|
-
|
|
60
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
61
|
-
|-----|------|-------------|----------|
|
|
62
|
-
| `playwright` | NPX | Testing E2E con Playwright | Node.js |
|
|
63
|
-
| `chrome-devtools` | NPX | Control de Chrome DevTools | Chrome instalado |
|
|
64
|
-
|
|
65
|
-
### Mobile - `mobile`
|
|
66
|
-
|
|
67
|
-
| MCP | Tipo | Descripción | Requiere |
|
|
68
|
-
|-----|------|-------------|----------|
|
|
69
|
-
| `ios-simulator` | NPX | Control de iOS Simulator | Xcode + macOS |
|
|
70
|
-
|
|
71
|
-
---
|
|
72
|
-
|
|
73
|
-
## Configuración de MCPs
|
|
74
|
-
|
|
75
|
-
### Tipo HTTP (servicios remotos)
|
|
76
|
-
|
|
77
|
-
Estos MCPs se conectan a servicios via URL. Se agregan a `~/.claude.json`:
|
|
78
|
-
|
|
79
|
-
```json
|
|
80
|
-
{
|
|
81
|
-
"mcpServers": {
|
|
82
|
-
"{nombre}": {
|
|
83
|
-
"type": "http",
|
|
84
|
-
"url": "{url}"
|
|
85
|
-
}
|
|
86
|
-
}
|
|
87
|
-
}
|
|
88
|
-
```
|
|
89
|
-
|
|
90
|
-
### Tipo NPX (comandos locales)
|
|
91
|
-
|
|
92
|
-
Estos MCPs ejecutan comandos localmente:
|
|
93
|
-
|
|
94
|
-
```json
|
|
95
|
-
{
|
|
96
|
-
"mcpServers": {
|
|
97
|
-
"{nombre}": {
|
|
98
|
-
"command": "npx",
|
|
99
|
-
"args": ["-y", "{package}@latest"],
|
|
100
|
-
"env": {
|
|
101
|
-
"VAR": "value"
|
|
102
|
-
}
|
|
103
|
-
}
|
|
104
|
-
}
|
|
105
|
-
}
|
|
106
|
-
```
|
|
107
|
-
|
|
108
|
-
---
|
|
109
|
-
|
|
110
|
-
## Instalación por MCP
|
|
111
|
-
|
|
112
|
-
### Context7 (Documentación de librerías)
|
|
113
|
-
|
|
114
|
-
**Recomendado para:** Todos los proyectos
|
|
115
|
-
|
|
116
|
-
```bash
|
|
117
|
-
# 1. Obtener API Key gratis en https://context7.com
|
|
118
|
-
# 2. Agregar a configuración de proyecto
|
|
119
|
-
```
|
|
120
|
-
|
|
121
|
-
**Configuración:**
|
|
122
|
-
```json
|
|
123
|
-
{
|
|
124
|
-
"context7": {
|
|
125
|
-
"type": "http",
|
|
126
|
-
"url": "https://mcp.context7.com/mcp",
|
|
127
|
-
"headers": {
|
|
128
|
-
"CONTEXT7_API_KEY": "{tu-api-key}"
|
|
129
|
-
}
|
|
130
|
-
}
|
|
131
|
-
}
|
|
132
|
-
```
|
|
133
|
-
|
|
134
|
-
**Uso:**
|
|
135
|
-
- Buscar documentación actualizada de cualquier librería
|
|
136
|
-
- Ejemplos de código actualizados
|
|
137
|
-
- Compatible con Next.js, React, Supabase, etc.
|
|
138
|
-
|
|
139
|
-
---
|
|
140
|
-
|
|
141
|
-
### Figma (Diseños)
|
|
142
|
-
|
|
143
|
-
**Recomendado para:** Proyectos con diseño UI/UX
|
|
144
|
-
|
|
145
|
-
```json
|
|
146
|
-
{
|
|
147
|
-
"figma": {
|
|
148
|
-
"type": "http",
|
|
149
|
-
"url": "https://mcp.figma.com/mcp"
|
|
150
|
-
}
|
|
151
|
-
}
|
|
152
|
-
```
|
|
153
|
-
|
|
154
|
-
**Uso:**
|
|
155
|
-
- Acceder a componentes de Figma
|
|
156
|
-
- Extraer estilos y colores
|
|
157
|
-
- Convertir diseños a código
|
|
158
|
-
|
|
159
|
-
---
|
|
160
|
-
|
|
161
|
-
### Supabase (Base de datos)
|
|
162
|
-
|
|
163
|
-
**Recomendado para:** Proyectos con Supabase
|
|
164
|
-
|
|
165
|
-
```bash
|
|
166
|
-
# 1. Obtener Access Token en https://supabase.com/dashboard/account/tokens
|
|
167
|
-
# 2. Obtener Project Ref de tu proyecto
|
|
168
|
-
```
|
|
169
|
-
|
|
170
|
-
**Configuración:**
|
|
171
|
-
```json
|
|
172
|
-
{
|
|
173
|
-
"supabase": {
|
|
174
|
-
"command": "npx",
|
|
175
|
-
"args": [
|
|
176
|
-
"-y",
|
|
177
|
-
"@supabase/mcp-server-supabase@latest",
|
|
178
|
-
"--read-only",
|
|
179
|
-
"--project-ref={tu-project-ref}"
|
|
180
|
-
],
|
|
181
|
-
"env": {
|
|
182
|
-
"SUPABASE_ACCESS_TOKEN": "{tu-access-token}"
|
|
183
|
-
}
|
|
184
|
-
}
|
|
185
|
-
}
|
|
186
|
-
```
|
|
187
|
-
|
|
188
|
-
**Uso:**
|
|
189
|
-
- Consultar schema de BD
|
|
190
|
-
- Ejecutar queries (read-only por defecto)
|
|
191
|
-
- Ver tablas y relaciones
|
|
192
|
-
|
|
193
|
-
---
|
|
194
|
-
|
|
195
|
-
### Playwright (Testing E2E)
|
|
196
|
-
|
|
197
|
-
**Recomendado para:** Testing de aplicaciones web
|
|
198
|
-
|
|
199
|
-
```json
|
|
200
|
-
{
|
|
201
|
-
"playwright": {
|
|
202
|
-
"command": "npx",
|
|
203
|
-
"args": ["-y", "@anthropic/mcp-server-playwright@latest"]
|
|
204
|
-
}
|
|
205
|
-
}
|
|
206
|
-
```
|
|
207
|
-
|
|
208
|
-
**Uso:**
|
|
209
|
-
- Testing end-to-end automatizado
|
|
210
|
-
- Screenshots y grabación de videos
|
|
211
|
-
- Testing cross-browser (Chrome, Firefox, Safari)
|
|
212
|
-
- Assertions y validaciones
|
|
213
|
-
|
|
214
|
-
---
|
|
215
|
-
|
|
216
|
-
### iOS Simulator (Mobile Testing)
|
|
217
|
-
|
|
218
|
-
**Recomendado para:** Desarrollo y testing de apps iOS
|
|
219
|
-
|
|
220
|
-
```json
|
|
221
|
-
{
|
|
222
|
-
"ios-simulator": {
|
|
223
|
-
"command": "npx",
|
|
224
|
-
"args": ["-y", "@anthropic/mcp-server-ios-simulator@latest"]
|
|
225
|
-
}
|
|
226
|
-
}
|
|
227
|
-
```
|
|
228
|
-
|
|
229
|
-
**Uso:**
|
|
230
|
-
- Controlar iOS Simulator programáticamente
|
|
231
|
-
- Tomar screenshots de apps
|
|
232
|
-
- Instalar y ejecutar apps
|
|
233
|
-
- Testing de UI móvil
|
|
234
|
-
|
|
235
|
-
**Requisitos:**
|
|
236
|
-
- macOS
|
|
237
|
-
- Xcode instalado
|
|
238
|
-
- iOS Simulator configurado
|
|
239
|
-
|
|
240
|
-
---
|
|
241
|
-
|
|
242
|
-
### Notion (Documentación)
|
|
243
|
-
|
|
244
|
-
**Recomendado para:** Equipos usando Notion
|
|
245
|
-
|
|
246
|
-
```json
|
|
247
|
-
{
|
|
248
|
-
"notion": {
|
|
249
|
-
"type": "http",
|
|
250
|
-
"url": "https://mcp.notion.com/mcp"
|
|
251
|
-
}
|
|
252
|
-
}
|
|
253
|
-
```
|
|
254
|
-
|
|
255
|
-
**Uso:**
|
|
256
|
-
- Acceder a páginas de Notion
|
|
257
|
-
- Leer documentación del equipo
|
|
258
|
-
- Crear notas
|
|
259
|
-
|
|
260
|
-
---
|
|
261
|
-
|
|
262
|
-
### Vercel (Deploy)
|
|
263
|
-
|
|
264
|
-
**Recomendado para:** Proyectos desplegados en Vercel
|
|
265
|
-
|
|
266
|
-
```json
|
|
267
|
-
{
|
|
268
|
-
"vercel": {
|
|
269
|
-
"type": "http",
|
|
270
|
-
"url": "https://mcp.vercel.com/"
|
|
271
|
-
}
|
|
272
|
-
}
|
|
273
|
-
```
|
|
274
|
-
|
|
275
|
-
**Uso:**
|
|
276
|
-
- Ver deployments
|
|
277
|
-
- Acceder a logs
|
|
278
|
-
- Gestionar proyectos
|
|
279
|
-
|
|
280
|
-
---
|
|
281
|
-
|
|
282
|
-
### Chrome DevTools (Browser)
|
|
283
|
-
|
|
284
|
-
**Recomendado para:** Testing y debugging de UI
|
|
285
|
-
|
|
286
|
-
```json
|
|
287
|
-
{
|
|
288
|
-
"chrome-devtools": {
|
|
289
|
-
"command": "npx",
|
|
290
|
-
"args": ["-y", "chrome-devtools-mcp@latest"]
|
|
291
|
-
}
|
|
292
|
-
}
|
|
293
|
-
```
|
|
294
|
-
|
|
295
|
-
**Uso:**
|
|
296
|
-
- Controlar Chrome programáticamente
|
|
297
|
-
- Tomar screenshots
|
|
298
|
-
- Inspeccionar elementos
|
|
299
|
-
- Debugging de frontend
|
|
300
|
-
|
|
301
|
-
---
|
|
302
|
-
|
|
303
|
-
## Proceso de Instalación
|
|
304
|
-
|
|
305
|
-
### Paso 1: Verificar configuración actual
|
|
306
|
-
|
|
307
|
-
```bash
|
|
308
|
-
# Ver MCPs configurados globalmente
|
|
309
|
-
cat ~/.claude.json | grep -A 20 '"mcpServers"'
|
|
310
|
-
|
|
311
|
-
# Ver MCPs del proyecto actual
|
|
312
|
-
cat .claude.json 2>/dev/null | grep -A 20 '"mcpServers"'
|
|
313
|
-
```
|
|
314
|
-
|
|
315
|
-
### Paso 2: Elegir nivel de configuración
|
|
316
|
-
|
|
317
|
-
- **Global** (`~/.claude.json`): Disponible en todos los proyectos
|
|
318
|
-
- **Proyecto** (`.claude.json` o `~/.claude.json` bajo "projects"): Solo en proyecto específico
|
|
319
|
-
|
|
320
|
-
### Paso 3: Agregar configuración
|
|
321
|
-
|
|
322
|
-
Para agregar a nivel de proyecto, crear/editar `.mcp.json` en la raíz:
|
|
323
|
-
|
|
324
|
-
```json
|
|
325
|
-
{
|
|
326
|
-
"mcpServers": {
|
|
327
|
-
"context7": {
|
|
328
|
-
"type": "http",
|
|
329
|
-
"url": "https://mcp.context7.com/mcp",
|
|
330
|
-
"headers": {
|
|
331
|
-
"CONTEXT7_API_KEY": "tu-key-aqui"
|
|
332
|
-
}
|
|
333
|
-
},
|
|
334
|
-
"figma": {
|
|
335
|
-
"type": "http",
|
|
336
|
-
"url": "https://mcp.figma.com/mcp"
|
|
337
|
-
}
|
|
338
|
-
}
|
|
339
|
-
}
|
|
340
|
-
```
|
|
341
|
-
|
|
342
|
-
### Paso 4: Reiniciar Claude Code
|
|
343
|
-
|
|
344
|
-
```bash
|
|
345
|
-
# Los MCPs se cargan al iniciar
|
|
346
|
-
# Salir y volver a entrar a Claude Code
|
|
347
|
-
```
|
|
348
|
-
|
|
349
|
-
---
|
|
350
|
-
|
|
351
|
-
## Verificar MCPs Activos
|
|
352
|
-
|
|
353
|
-
Dentro de Claude Code:
|
|
354
|
-
```
|
|
355
|
-
/mcp
|
|
356
|
-
```
|
|
357
|
-
|
|
358
|
-
Muestra los MCPs conectados y sus herramientas disponibles.
|
|
359
|
-
|
|
360
|
-
---
|
|
361
|
-
|
|
362
|
-
## MCPs Recomendados por Tipo de Proyecto
|
|
363
|
-
|
|
364
|
-
### Web App (Next.js/React)
|
|
365
|
-
```
|
|
366
|
-
context7 → Documentación actualizada
|
|
367
|
-
figma → Diseños (si aplica)
|
|
368
|
-
vercel → Deploy
|
|
369
|
-
playwright → Testing E2E
|
|
370
|
-
chrome-devtools → Debugging
|
|
371
|
-
```
|
|
372
|
-
|
|
373
|
-
### Backend/API
|
|
374
|
-
```
|
|
375
|
-
context7 → Documentación
|
|
376
|
-
supabase → Base de datos (si aplica)
|
|
377
|
-
```
|
|
378
|
-
|
|
379
|
-
### Mobile iOS
|
|
380
|
-
```
|
|
381
|
-
context7 → Documentación
|
|
382
|
-
figma → Diseños
|
|
383
|
-
ios-simulator → Testing en simulador
|
|
384
|
-
```
|
|
385
|
-
|
|
386
|
-
### Mobile React Native/Flutter
|
|
387
|
-
```
|
|
388
|
-
context7 → Documentación
|
|
389
|
-
figma → Diseños
|
|
390
|
-
ios-simulator → Testing iOS
|
|
391
|
-
chrome-devtools → Debugging web views
|
|
392
|
-
```
|
|
393
|
-
|
|
394
|
-
### Full Stack
|
|
395
|
-
```
|
|
396
|
-
context7 → Documentación
|
|
397
|
-
supabase → Base de datos
|
|
398
|
-
figma → Diseños
|
|
399
|
-
vercel → Deploy
|
|
400
|
-
playwright → Testing E2E
|
|
401
|
-
```
|
|
402
|
-
|
|
403
|
-
---
|
|
404
|
-
|
|
405
|
-
## Output
|
|
406
|
-
|
|
407
|
-
```
|
|
408
|
-
╔══════════════════════════════════════════════════════════════╗
|
|
409
|
-
║ ODEN FORGE - MCP INSTALLED ║
|
|
410
|
-
╠══════════════════════════════════════════════════════════════╣
|
|
411
|
-
║ ║
|
|
412
|
-
║ CONFIGURACIÓN AGREGADA A: .mcp.json ║
|
|
413
|
-
║ ║
|
|
414
|
-
║ MCPs INSTALADOS: ║
|
|
415
|
-
║ ├─ context7 → Documentación de librerías ║
|
|
416
|
-
║ ├─ figma → Acceso a diseños ║
|
|
417
|
-
║ └─ vercel → Deploy management ║
|
|
418
|
-
║ ║
|
|
419
|
-
║ PRÓXIMOS PASOS: ║
|
|
420
|
-
║ 1. Reiniciar Claude Code para cargar MCPs ║
|
|
421
|
-
║ 2. Verificar con /mcp ║
|
|
422
|
-
║ 3. Configurar API keys si es necesario ║
|
|
423
|
-
║ ║
|
|
424
|
-
╚══════════════════════════════════════════════════════════════╝
|
|
425
|
-
```
|
|
426
|
-
|
|
427
|
-
---
|
|
428
|
-
|
|
429
|
-
## Notas
|
|
430
|
-
|
|
431
|
-
- Los MCPs HTTP requieren autenticación OAuth la primera vez
|
|
432
|
-
- Los MCPs NPX se ejecutan localmente
|
|
433
|
-
- Algunos MCPs requieren API keys (ej: Context7, Supabase)
|
|
434
|
-
- La configuración de MCPs está en `~/.claude.json` o `.mcp.json`
|
|
435
|
-
|
|
436
|
-
---
|
|
437
|
-
|
|
438
|
-
## Agregar MCP Personalizado
|
|
439
|
-
|
|
440
|
-
Si quieres agregar un MCP que no está en la lista:
|
|
441
|
-
|
|
442
|
-
```json
|
|
443
|
-
{
|
|
444
|
-
"mi-mcp": {
|
|
445
|
-
"type": "http",
|
|
446
|
-
"url": "https://mcp.mi-servicio.com/mcp"
|
|
447
|
-
}
|
|
448
|
-
}
|
|
449
|
-
```
|
|
450
|
-
|
|
451
|
-
O para MCPs locales:
|
|
452
|
-
|
|
453
|
-
```json
|
|
454
|
-
{
|
|
455
|
-
"mi-mcp-local": {
|
|
456
|
-
"command": "npx",
|
|
457
|
-
"args": ["-y", "@org/mcp-server@latest"]
|
|
458
|
-
}
|
|
459
|
-
}
|
|
460
|
-
```
|