cmp-standards 2.7.0 → 2.8.0-alpha
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/README.md +633 -633
- package/dist/cache/EmbeddingCache.d.ts +109 -0
- package/dist/cache/EmbeddingCache.d.ts.map +1 -0
- package/dist/cache/EmbeddingCache.js +239 -0
- package/dist/cache/EmbeddingCache.js.map +1 -0
- package/dist/cache/index.d.ts +6 -0
- package/dist/cache/index.d.ts.map +1 -0
- package/dist/cache/index.js +6 -0
- package/dist/cache/index.js.map +1 -0
- package/dist/cli/index.js +0 -0
- package/dist/db/turso-client.js +11 -11
- package/dist/eslint/rules/no-async-useeffect.js +6 -6
- package/dist/events/EventBus.d.ts +87 -0
- package/dist/events/EventBus.d.ts.map +1 -0
- package/dist/events/EventBus.js +200 -0
- package/dist/events/EventBus.js.map +1 -0
- package/dist/events/index.d.ts +7 -0
- package/dist/events/index.d.ts.map +1 -0
- package/dist/events/index.js +9 -0
- package/dist/events/index.js.map +1 -0
- package/dist/events/types.d.ts +989 -0
- package/dist/events/types.d.ts.map +1 -0
- package/dist/events/types.js +136 -0
- package/dist/events/types.js.map +1 -0
- package/dist/experts/ConsensusEngine.d.ts +57 -0
- package/dist/experts/ConsensusEngine.d.ts.map +1 -0
- package/dist/experts/ConsensusEngine.js +146 -0
- package/dist/experts/ConsensusEngine.js.map +1 -0
- package/dist/experts/ExpertPanelService.d.ts +84 -0
- package/dist/experts/ExpertPanelService.d.ts.map +1 -0
- package/dist/experts/ExpertPanelService.js +204 -0
- package/dist/experts/ExpertPanelService.js.map +1 -0
- package/dist/experts/ExpertRouter.d.ts +68 -0
- package/dist/experts/ExpertRouter.d.ts.map +1 -0
- package/dist/experts/ExpertRouter.js +374 -0
- package/dist/experts/ExpertRouter.js.map +1 -0
- package/dist/experts/VoteCollector.d.ts +58 -0
- package/dist/experts/VoteCollector.d.ts.map +1 -0
- package/dist/experts/VoteCollector.js +146 -0
- package/dist/experts/VoteCollector.js.map +1 -0
- package/dist/experts/index.d.ts +9 -0
- package/dist/experts/index.d.ts.map +1 -0
- package/dist/experts/index.js +13 -0
- package/dist/experts/index.js.map +1 -0
- package/dist/hooks/cloud-pre-tool-use.js +20 -20
- package/dist/hooks/expert-review.d.ts +74 -0
- package/dist/hooks/expert-review.d.ts.map +1 -0
- package/dist/hooks/expert-review.js +220 -0
- package/dist/hooks/expert-review.js.map +1 -0
- package/dist/hooks/index.d.ts +1 -0
- package/dist/hooks/index.d.ts.map +1 -1
- package/dist/hooks/index.js +2 -0
- package/dist/hooks/index.js.map +1 -1
- package/dist/index.d.ts +13 -0
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +22 -0
- package/dist/index.js.map +1 -1
- package/dist/performance/Debouncer.d.ts +91 -0
- package/dist/performance/Debouncer.d.ts.map +1 -0
- package/dist/performance/Debouncer.js +198 -0
- package/dist/performance/Debouncer.js.map +1 -0
- package/dist/performance/MemoryDecay.d.ts +82 -0
- package/dist/performance/MemoryDecay.d.ts.map +1 -0
- package/dist/performance/MemoryDecay.js +153 -0
- package/dist/performance/MemoryDecay.js.map +1 -0
- package/dist/performance/index.d.ts +7 -0
- package/dist/performance/index.d.ts.map +1 -0
- package/dist/performance/index.js +9 -0
- package/dist/performance/index.js.map +1 -0
- package/dist/schema/expert-types.d.ts +395 -0
- package/dist/schema/expert-types.d.ts.map +1 -0
- package/dist/schema/expert-types.js +250 -0
- package/dist/schema/expert-types.js.map +1 -0
- package/dist/services/ContextGenerator.js +7 -7
- package/dist/services/ProjectScaffold.js +76 -76
- package/dist/services/memory-router.js +35 -35
- package/dist/services/pattern-tracker.js +90 -90
- package/dist/services/semantic-search.js +2 -2
- package/package.json +105 -104
- package/standards/README.md +50 -50
- package/standards/experts/expert-routing.md +215 -215
- package/standards/general/code-quality.md +86 -86
- package/standards/general/memory-usage.md +205 -205
- package/standards/general/sync-workflow.md +235 -235
- package/standards/general/workflow.md +82 -82
- package/standards/hooks/mandatory-tracking.md +446 -446
- package/standards/infrastructure/cloud-database.md +287 -287
- package/standards/mcp/server-design.md +243 -243
- package/standards/mcp/tool-patterns.md +354 -354
- package/standards/skills/skill-structure.md +286 -286
- package/standards/skills/workflow-design.md +323 -323
- package/standards/tools/tool-design.md +297 -297
- package/templates/agents/architecture-expert.md +61 -61
- package/templates/agents/database-expert.md +62 -62
- package/templates/agents/documentation-expert.md +57 -57
- package/templates/agents/memory-expert.md +88 -88
- package/templates/agents/performance-expert.md +61 -61
- package/templates/agents/security-expert.md +59 -59
- package/templates/agents/ux-expert.md +63 -63
- package/templates/agents/worker.md +75 -75
- package/templates/ai-skills/SKILL_TEMPLATE.md +55 -55
- package/templates/claude-settings.json +72 -72
- package/templates/commands/experts.md +138 -138
- package/templates/hooks/README.md +158 -158
- package/templates/hooks/project.config.json.template +77 -77
- package/templates/hooks/settings.local.json.template +57 -57
- package/templates/memory-config.json +56 -56
- package/templates/memory-config.schema.json +212 -212
- package/templates/settings.json +58 -58
- package/templates/skills/continue.md +205 -205
- package/templates/workflows/business-improvement.md +264 -264
- package/templates/workflows/expert-review.md +153 -153
- package/templates/workflows/internal-app.md +245 -245
- package/templates/workflows/sync-docs.md +187 -187
|
@@ -1,323 +1,323 @@
|
|
|
1
|
-
# Diseño de Workflows con Skills
|
|
2
|
-
|
|
3
|
-
## Concepto
|
|
4
|
-
|
|
5
|
-
Un **workflow** es una secuencia de pasos que Claude ejecuta. Las skills definen workflows reutilizables.
|
|
6
|
-
|
|
7
|
-
## Tipos de Workflows
|
|
8
|
-
|
|
9
|
-
### 1. Linear Workflow
|
|
10
|
-
|
|
11
|
-
Pasos en secuencia:
|
|
12
|
-
|
|
13
|
-
```markdown
|
|
14
|
-
---
|
|
15
|
-
name: deploy
|
|
16
|
-
description: Deploy to production
|
|
17
|
-
---
|
|
18
|
-
|
|
19
|
-
# Deploy Workflow
|
|
20
|
-
|
|
21
|
-
## Steps (execute in order)
|
|
22
|
-
|
|
23
|
-
1. **Verify** - Run tests and typecheck
|
|
24
|
-
2. **Build** - Create production build
|
|
25
|
-
3. **Deploy** - Push to production
|
|
26
|
-
4. **Verify** - Check deployment health
|
|
27
|
-
```
|
|
28
|
-
|
|
29
|
-
### 2. Branching Workflow
|
|
30
|
-
|
|
31
|
-
Decisiones basadas en condiciones:
|
|
32
|
-
|
|
33
|
-
```markdown
|
|
34
|
-
---
|
|
35
|
-
name: fix-issue
|
|
36
|
-
description: Fix a reported issue
|
|
37
|
-
arguments:
|
|
38
|
-
- name: issueType
|
|
39
|
-
enum: [bug, performance, security]
|
|
40
|
-
---
|
|
41
|
-
|
|
42
|
-
# Fix Issue
|
|
43
|
-
|
|
44
|
-
## Analyze
|
|
45
|
-
|
|
46
|
-
First, identify the type of issue.
|
|
47
|
-
|
|
48
|
-
## If bug
|
|
49
|
-
1. Reproduce the issue
|
|
50
|
-
2. Write failing test
|
|
51
|
-
3. Fix the code
|
|
52
|
-
4. Verify test passes
|
|
53
|
-
|
|
54
|
-
## If performance
|
|
55
|
-
1. Profile the code
|
|
56
|
-
2. Identify bottleneck
|
|
57
|
-
3. Optimize
|
|
58
|
-
4. Benchmark improvement
|
|
59
|
-
|
|
60
|
-
## If security
|
|
61
|
-
1. Assess severity
|
|
62
|
-
2. Create fix
|
|
63
|
-
3. Run security scan
|
|
64
|
-
4. Document in changelog
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
### 3. Iterative Workflow
|
|
68
|
-
|
|
69
|
-
Repetir hasta condición:
|
|
70
|
-
|
|
71
|
-
```markdown
|
|
72
|
-
---
|
|
73
|
-
name: refactor
|
|
74
|
-
description: Iterative refactoring
|
|
75
|
-
---
|
|
76
|
-
|
|
77
|
-
# Refactor Workflow
|
|
78
|
-
|
|
79
|
-
## Loop until complete
|
|
80
|
-
|
|
81
|
-
1. **Identify** next refactoring opportunity
|
|
82
|
-
2. **Apply** refactoring
|
|
83
|
-
3. **Verify** tests still pass
|
|
84
|
-
4. **Check** if more refactoring needed
|
|
85
|
-
- If yes: continue to step 1
|
|
86
|
-
- If no: complete workflow
|
|
87
|
-
```
|
|
88
|
-
|
|
89
|
-
### 4. Parallel Workflow
|
|
90
|
-
|
|
91
|
-
Tareas independientes en paralelo:
|
|
92
|
-
|
|
93
|
-
```markdown
|
|
94
|
-
---
|
|
95
|
-
name: full-check
|
|
96
|
-
description: Run all checks
|
|
97
|
-
---
|
|
98
|
-
|
|
99
|
-
# Full Check Workflow
|
|
100
|
-
|
|
101
|
-
## Run in parallel
|
|
102
|
-
|
|
103
|
-
Execute these independently:
|
|
104
|
-
- `npm run typecheck`
|
|
105
|
-
- `npm run lint`
|
|
106
|
-
- `npm run test`
|
|
107
|
-
- `npm run build`
|
|
108
|
-
|
|
109
|
-
## Collect results
|
|
110
|
-
|
|
111
|
-
Report status of all checks.
|
|
112
|
-
```
|
|
113
|
-
|
|
114
|
-
## Integración con Expertos
|
|
115
|
-
|
|
116
|
-
Para decisiones críticas, consultar `/experts`:
|
|
117
|
-
|
|
118
|
-
```markdown
|
|
119
|
-
---
|
|
120
|
-
name: implement-feature
|
|
121
|
-
description: Implement a new feature with expert review
|
|
122
|
-
---
|
|
123
|
-
|
|
124
|
-
# Implement Feature
|
|
125
|
-
|
|
126
|
-
## 1. Plan
|
|
127
|
-
|
|
128
|
-
Create implementation plan using TodoWrite.
|
|
129
|
-
|
|
130
|
-
## 2. Implement
|
|
131
|
-
|
|
132
|
-
Execute the plan step by step.
|
|
133
|
-
|
|
134
|
-
## 3. Expert Review
|
|
135
|
-
|
|
136
|
-
If touching critical paths (finance, auth, schema):
|
|
137
|
-
|
|
138
|
-
```
|
|
139
|
-
/experts [modified files]
|
|
140
|
-
```
|
|
141
|
-
|
|
142
|
-
Wait for approval before proceeding.
|
|
143
|
-
|
|
144
|
-
## 4. Finalize
|
|
145
|
-
|
|
146
|
-
If approved:
|
|
147
|
-
- Run final verification
|
|
148
|
-
- Create commit
|
|
149
|
-
|
|
150
|
-
If rejected:
|
|
151
|
-
- Address feedback
|
|
152
|
-
- Return to step 2
|
|
153
|
-
```
|
|
154
|
-
|
|
155
|
-
## Workflows Estándar Recomendados
|
|
156
|
-
|
|
157
|
-
### Feature Development
|
|
158
|
-
|
|
159
|
-
```markdown
|
|
160
|
-
1. Understand requirements
|
|
161
|
-
2. Create plan (TodoWrite)
|
|
162
|
-
3. Implement incrementally
|
|
163
|
-
4. Write tests for critical paths
|
|
164
|
-
5. Run verification (typecheck, lint)
|
|
165
|
-
6. Expert review if critical
|
|
166
|
-
7. Commit changes
|
|
167
|
-
```
|
|
168
|
-
|
|
169
|
-
### Bug Fix
|
|
170
|
-
|
|
171
|
-
```markdown
|
|
172
|
-
1. Reproduce issue
|
|
173
|
-
2. Identify root cause
|
|
174
|
-
3. Write failing test
|
|
175
|
-
4. Implement fix
|
|
176
|
-
5. Verify test passes
|
|
177
|
-
6. Check for regressions
|
|
178
|
-
7. Commit with issue reference
|
|
179
|
-
```
|
|
180
|
-
|
|
181
|
-
### Refactoring
|
|
182
|
-
|
|
183
|
-
```markdown
|
|
184
|
-
1. Identify scope
|
|
185
|
-
2. Ensure test coverage
|
|
186
|
-
3. Small, incremental changes
|
|
187
|
-
4. Run tests after each change
|
|
188
|
-
5. No behavior changes
|
|
189
|
-
6. Commit atomically
|
|
190
|
-
```
|
|
191
|
-
|
|
192
|
-
## Estado y Tracking
|
|
193
|
-
|
|
194
|
-
Usar TodoWrite para tracking:
|
|
195
|
-
|
|
196
|
-
```markdown
|
|
197
|
-
## Tracking
|
|
198
|
-
|
|
199
|
-
Use TodoWrite to:
|
|
200
|
-
- Create tasks at workflow start
|
|
201
|
-
- Update status as you progress
|
|
202
|
-
- Mark completed when done
|
|
203
|
-
- Add discovered tasks as needed
|
|
204
|
-
```
|
|
205
|
-
|
|
206
|
-
## Memory Integration
|
|
207
|
-
|
|
208
|
-
Registrar aprendizajes:
|
|
209
|
-
|
|
210
|
-
```markdown
|
|
211
|
-
## Learning Capture
|
|
212
|
-
|
|
213
|
-
During workflow:
|
|
214
|
-
- Capture new patterns discovered
|
|
215
|
-
- Note gotchas for future reference
|
|
216
|
-
- Record decisions made and why
|
|
217
|
-
|
|
218
|
-
Use memory tools to persist learnings.
|
|
219
|
-
```
|
|
220
|
-
|
|
221
|
-
## Error Handling
|
|
222
|
-
|
|
223
|
-
```markdown
|
|
224
|
-
## If errors occur
|
|
225
|
-
|
|
226
|
-
1. **Log** the error context
|
|
227
|
-
2. **Analyze** root cause
|
|
228
|
-
3. **Decide** next action:
|
|
229
|
-
- Retry if transient
|
|
230
|
-
- Ask user if unclear
|
|
231
|
-
- Abort if unrecoverable
|
|
232
|
-
4. **Document** the issue if new pattern
|
|
233
|
-
```
|
|
234
|
-
|
|
235
|
-
## Composing Workflows
|
|
236
|
-
|
|
237
|
-
Skills pueden llamar otras skills:
|
|
238
|
-
|
|
239
|
-
```markdown
|
|
240
|
-
---
|
|
241
|
-
name: release
|
|
242
|
-
description: Full release workflow
|
|
243
|
-
---
|
|
244
|
-
|
|
245
|
-
# Release
|
|
246
|
-
|
|
247
|
-
## Steps
|
|
248
|
-
|
|
249
|
-
1. Run `/full-check` - all validations
|
|
250
|
-
2. Run `/changelog` - update changelog
|
|
251
|
-
3. Run `/version-bump` - increment version
|
|
252
|
-
4. Run `/deploy` - push to production
|
|
253
|
-
5. Run `/notify` - send notifications
|
|
254
|
-
```
|
|
255
|
-
|
|
256
|
-
## Ejemplo Completo
|
|
257
|
-
|
|
258
|
-
```markdown
|
|
259
|
-
---
|
|
260
|
-
name: add-api-endpoint
|
|
261
|
-
description: Add new TRPC endpoint with full workflow
|
|
262
|
-
arguments:
|
|
263
|
-
- name: routerName
|
|
264
|
-
required: true
|
|
265
|
-
- name: procedureName
|
|
266
|
-
required: true
|
|
267
|
-
---
|
|
268
|
-
|
|
269
|
-
# Add API Endpoint: {{routerName}}.{{procedureName}}
|
|
270
|
-
|
|
271
|
-
## 1. Setup Tasks
|
|
272
|
-
|
|
273
|
-
Create TodoWrite entries:
|
|
274
|
-
- [ ] Create procedure in router
|
|
275
|
-
- [ ] Add Zod schema
|
|
276
|
-
- [ ] Write tests
|
|
277
|
-
- [ ] Update client types
|
|
278
|
-
|
|
279
|
-
## 2. Implementation
|
|
280
|
-
|
|
281
|
-
### 2.1 Locate Router
|
|
282
|
-
|
|
283
|
-
Find `src/server/api/routers/{{routerName}}.ts`
|
|
284
|
-
|
|
285
|
-
### 2.2 Add Procedure
|
|
286
|
-
|
|
287
|
-
```typescript
|
|
288
|
-
{{procedureName}}: protectedProcedure
|
|
289
|
-
.input({{procedureName}}Schema)
|
|
290
|
-
.mutation(async ({ ctx, input }) => {
|
|
291
|
-
// Implementation
|
|
292
|
-
})
|
|
293
|
-
```
|
|
294
|
-
|
|
295
|
-
### 2.3 Add Schema
|
|
296
|
-
|
|
297
|
-
```typescript
|
|
298
|
-
const {{procedureName}}Schema = z.object({
|
|
299
|
-
// Define input schema
|
|
300
|
-
})
|
|
301
|
-
```
|
|
302
|
-
|
|
303
|
-
## 3. Testing
|
|
304
|
-
|
|
305
|
-
Create test at `src/server/api/routers/__tests__/{{routerName}}.test.ts`
|
|
306
|
-
|
|
307
|
-
## 4. Verification
|
|
308
|
-
|
|
309
|
-
Run:
|
|
310
|
-
- `npm run typecheck`
|
|
311
|
-
- `npm run test -- {{routerName}}`
|
|
312
|
-
|
|
313
|
-
## 5. Expert Review
|
|
314
|
-
|
|
315
|
-
If {{routerName}} is in critical path:
|
|
316
|
-
```
|
|
317
|
-
/experts src/server/api/routers/{{routerName}}.ts
|
|
318
|
-
```
|
|
319
|
-
|
|
320
|
-
## 6. Complete
|
|
321
|
-
|
|
322
|
-
Mark all todos as completed.
|
|
323
|
-
```
|
|
1
|
+
# Diseño de Workflows con Skills
|
|
2
|
+
|
|
3
|
+
## Concepto
|
|
4
|
+
|
|
5
|
+
Un **workflow** es una secuencia de pasos que Claude ejecuta. Las skills definen workflows reutilizables.
|
|
6
|
+
|
|
7
|
+
## Tipos de Workflows
|
|
8
|
+
|
|
9
|
+
### 1. Linear Workflow
|
|
10
|
+
|
|
11
|
+
Pasos en secuencia:
|
|
12
|
+
|
|
13
|
+
```markdown
|
|
14
|
+
---
|
|
15
|
+
name: deploy
|
|
16
|
+
description: Deploy to production
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
# Deploy Workflow
|
|
20
|
+
|
|
21
|
+
## Steps (execute in order)
|
|
22
|
+
|
|
23
|
+
1. **Verify** - Run tests and typecheck
|
|
24
|
+
2. **Build** - Create production build
|
|
25
|
+
3. **Deploy** - Push to production
|
|
26
|
+
4. **Verify** - Check deployment health
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
### 2. Branching Workflow
|
|
30
|
+
|
|
31
|
+
Decisiones basadas en condiciones:
|
|
32
|
+
|
|
33
|
+
```markdown
|
|
34
|
+
---
|
|
35
|
+
name: fix-issue
|
|
36
|
+
description: Fix a reported issue
|
|
37
|
+
arguments:
|
|
38
|
+
- name: issueType
|
|
39
|
+
enum: [bug, performance, security]
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
# Fix Issue
|
|
43
|
+
|
|
44
|
+
## Analyze
|
|
45
|
+
|
|
46
|
+
First, identify the type of issue.
|
|
47
|
+
|
|
48
|
+
## If bug
|
|
49
|
+
1. Reproduce the issue
|
|
50
|
+
2. Write failing test
|
|
51
|
+
3. Fix the code
|
|
52
|
+
4. Verify test passes
|
|
53
|
+
|
|
54
|
+
## If performance
|
|
55
|
+
1. Profile the code
|
|
56
|
+
2. Identify bottleneck
|
|
57
|
+
3. Optimize
|
|
58
|
+
4. Benchmark improvement
|
|
59
|
+
|
|
60
|
+
## If security
|
|
61
|
+
1. Assess severity
|
|
62
|
+
2. Create fix
|
|
63
|
+
3. Run security scan
|
|
64
|
+
4. Document in changelog
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
### 3. Iterative Workflow
|
|
68
|
+
|
|
69
|
+
Repetir hasta condición:
|
|
70
|
+
|
|
71
|
+
```markdown
|
|
72
|
+
---
|
|
73
|
+
name: refactor
|
|
74
|
+
description: Iterative refactoring
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
# Refactor Workflow
|
|
78
|
+
|
|
79
|
+
## Loop until complete
|
|
80
|
+
|
|
81
|
+
1. **Identify** next refactoring opportunity
|
|
82
|
+
2. **Apply** refactoring
|
|
83
|
+
3. **Verify** tests still pass
|
|
84
|
+
4. **Check** if more refactoring needed
|
|
85
|
+
- If yes: continue to step 1
|
|
86
|
+
- If no: complete workflow
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### 4. Parallel Workflow
|
|
90
|
+
|
|
91
|
+
Tareas independientes en paralelo:
|
|
92
|
+
|
|
93
|
+
```markdown
|
|
94
|
+
---
|
|
95
|
+
name: full-check
|
|
96
|
+
description: Run all checks
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
# Full Check Workflow
|
|
100
|
+
|
|
101
|
+
## Run in parallel
|
|
102
|
+
|
|
103
|
+
Execute these independently:
|
|
104
|
+
- `npm run typecheck`
|
|
105
|
+
- `npm run lint`
|
|
106
|
+
- `npm run test`
|
|
107
|
+
- `npm run build`
|
|
108
|
+
|
|
109
|
+
## Collect results
|
|
110
|
+
|
|
111
|
+
Report status of all checks.
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
## Integración con Expertos
|
|
115
|
+
|
|
116
|
+
Para decisiones críticas, consultar `/experts`:
|
|
117
|
+
|
|
118
|
+
```markdown
|
|
119
|
+
---
|
|
120
|
+
name: implement-feature
|
|
121
|
+
description: Implement a new feature with expert review
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
# Implement Feature
|
|
125
|
+
|
|
126
|
+
## 1. Plan
|
|
127
|
+
|
|
128
|
+
Create implementation plan using TodoWrite.
|
|
129
|
+
|
|
130
|
+
## 2. Implement
|
|
131
|
+
|
|
132
|
+
Execute the plan step by step.
|
|
133
|
+
|
|
134
|
+
## 3. Expert Review
|
|
135
|
+
|
|
136
|
+
If touching critical paths (finance, auth, schema):
|
|
137
|
+
|
|
138
|
+
```
|
|
139
|
+
/experts [modified files]
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
Wait for approval before proceeding.
|
|
143
|
+
|
|
144
|
+
## 4. Finalize
|
|
145
|
+
|
|
146
|
+
If approved:
|
|
147
|
+
- Run final verification
|
|
148
|
+
- Create commit
|
|
149
|
+
|
|
150
|
+
If rejected:
|
|
151
|
+
- Address feedback
|
|
152
|
+
- Return to step 2
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
## Workflows Estándar Recomendados
|
|
156
|
+
|
|
157
|
+
### Feature Development
|
|
158
|
+
|
|
159
|
+
```markdown
|
|
160
|
+
1. Understand requirements
|
|
161
|
+
2. Create plan (TodoWrite)
|
|
162
|
+
3. Implement incrementally
|
|
163
|
+
4. Write tests for critical paths
|
|
164
|
+
5. Run verification (typecheck, lint)
|
|
165
|
+
6. Expert review if critical
|
|
166
|
+
7. Commit changes
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
### Bug Fix
|
|
170
|
+
|
|
171
|
+
```markdown
|
|
172
|
+
1. Reproduce issue
|
|
173
|
+
2. Identify root cause
|
|
174
|
+
3. Write failing test
|
|
175
|
+
4. Implement fix
|
|
176
|
+
5. Verify test passes
|
|
177
|
+
6. Check for regressions
|
|
178
|
+
7. Commit with issue reference
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### Refactoring
|
|
182
|
+
|
|
183
|
+
```markdown
|
|
184
|
+
1. Identify scope
|
|
185
|
+
2. Ensure test coverage
|
|
186
|
+
3. Small, incremental changes
|
|
187
|
+
4. Run tests after each change
|
|
188
|
+
5. No behavior changes
|
|
189
|
+
6. Commit atomically
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
## Estado y Tracking
|
|
193
|
+
|
|
194
|
+
Usar TodoWrite para tracking:
|
|
195
|
+
|
|
196
|
+
```markdown
|
|
197
|
+
## Tracking
|
|
198
|
+
|
|
199
|
+
Use TodoWrite to:
|
|
200
|
+
- Create tasks at workflow start
|
|
201
|
+
- Update status as you progress
|
|
202
|
+
- Mark completed when done
|
|
203
|
+
- Add discovered tasks as needed
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
## Memory Integration
|
|
207
|
+
|
|
208
|
+
Registrar aprendizajes:
|
|
209
|
+
|
|
210
|
+
```markdown
|
|
211
|
+
## Learning Capture
|
|
212
|
+
|
|
213
|
+
During workflow:
|
|
214
|
+
- Capture new patterns discovered
|
|
215
|
+
- Note gotchas for future reference
|
|
216
|
+
- Record decisions made and why
|
|
217
|
+
|
|
218
|
+
Use memory tools to persist learnings.
|
|
219
|
+
```
|
|
220
|
+
|
|
221
|
+
## Error Handling
|
|
222
|
+
|
|
223
|
+
```markdown
|
|
224
|
+
## If errors occur
|
|
225
|
+
|
|
226
|
+
1. **Log** the error context
|
|
227
|
+
2. **Analyze** root cause
|
|
228
|
+
3. **Decide** next action:
|
|
229
|
+
- Retry if transient
|
|
230
|
+
- Ask user if unclear
|
|
231
|
+
- Abort if unrecoverable
|
|
232
|
+
4. **Document** the issue if new pattern
|
|
233
|
+
```
|
|
234
|
+
|
|
235
|
+
## Composing Workflows
|
|
236
|
+
|
|
237
|
+
Skills pueden llamar otras skills:
|
|
238
|
+
|
|
239
|
+
```markdown
|
|
240
|
+
---
|
|
241
|
+
name: release
|
|
242
|
+
description: Full release workflow
|
|
243
|
+
---
|
|
244
|
+
|
|
245
|
+
# Release
|
|
246
|
+
|
|
247
|
+
## Steps
|
|
248
|
+
|
|
249
|
+
1. Run `/full-check` - all validations
|
|
250
|
+
2. Run `/changelog` - update changelog
|
|
251
|
+
3. Run `/version-bump` - increment version
|
|
252
|
+
4. Run `/deploy` - push to production
|
|
253
|
+
5. Run `/notify` - send notifications
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
## Ejemplo Completo
|
|
257
|
+
|
|
258
|
+
```markdown
|
|
259
|
+
---
|
|
260
|
+
name: add-api-endpoint
|
|
261
|
+
description: Add new TRPC endpoint with full workflow
|
|
262
|
+
arguments:
|
|
263
|
+
- name: routerName
|
|
264
|
+
required: true
|
|
265
|
+
- name: procedureName
|
|
266
|
+
required: true
|
|
267
|
+
---
|
|
268
|
+
|
|
269
|
+
# Add API Endpoint: {{routerName}}.{{procedureName}}
|
|
270
|
+
|
|
271
|
+
## 1. Setup Tasks
|
|
272
|
+
|
|
273
|
+
Create TodoWrite entries:
|
|
274
|
+
- [ ] Create procedure in router
|
|
275
|
+
- [ ] Add Zod schema
|
|
276
|
+
- [ ] Write tests
|
|
277
|
+
- [ ] Update client types
|
|
278
|
+
|
|
279
|
+
## 2. Implementation
|
|
280
|
+
|
|
281
|
+
### 2.1 Locate Router
|
|
282
|
+
|
|
283
|
+
Find `src/server/api/routers/{{routerName}}.ts`
|
|
284
|
+
|
|
285
|
+
### 2.2 Add Procedure
|
|
286
|
+
|
|
287
|
+
```typescript
|
|
288
|
+
{{procedureName}}: protectedProcedure
|
|
289
|
+
.input({{procedureName}}Schema)
|
|
290
|
+
.mutation(async ({ ctx, input }) => {
|
|
291
|
+
// Implementation
|
|
292
|
+
})
|
|
293
|
+
```
|
|
294
|
+
|
|
295
|
+
### 2.3 Add Schema
|
|
296
|
+
|
|
297
|
+
```typescript
|
|
298
|
+
const {{procedureName}}Schema = z.object({
|
|
299
|
+
// Define input schema
|
|
300
|
+
})
|
|
301
|
+
```
|
|
302
|
+
|
|
303
|
+
## 3. Testing
|
|
304
|
+
|
|
305
|
+
Create test at `src/server/api/routers/__tests__/{{routerName}}.test.ts`
|
|
306
|
+
|
|
307
|
+
## 4. Verification
|
|
308
|
+
|
|
309
|
+
Run:
|
|
310
|
+
- `npm run typecheck`
|
|
311
|
+
- `npm run test -- {{routerName}}`
|
|
312
|
+
|
|
313
|
+
## 5. Expert Review
|
|
314
|
+
|
|
315
|
+
If {{routerName}} is in critical path:
|
|
316
|
+
```
|
|
317
|
+
/experts src/server/api/routers/{{routerName}}.ts
|
|
318
|
+
```
|
|
319
|
+
|
|
320
|
+
## 6. Complete
|
|
321
|
+
|
|
322
|
+
Mark all todos as completed.
|
|
323
|
+
```
|