telo3-ai 5.0.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/AI-CONTEXT.md +263 -0
- package/LICENSE +21 -0
- package/ONBOARDING-SKILL.md +728 -0
- package/README.md +801 -0
- package/SKILL-METADATA.json +237 -0
- package/SKILL.md +666 -0
- package/cli.js +84 -0
- package/index.js +65 -0
- package/package.json +97 -0
- package/references/accessibility-quality.md +278 -0
- package/references/ai-behavior.md +363 -0
- package/references/document-specification.md +425 -0
- package/references/legal-compliance.md +408 -0
- package/references/performance-quality.md +351 -0
- package/references/privacy-compliance.md +494 -0
- package/references/project-audit.md +468 -0
- package/references/security-quality.md +254 -0
- package/references/seo-quality.md +347 -0
- package/references/smart-skill-delegation.md +451 -0
- package/references/token-optimization.md +481 -0
- package/references/ui-quality.md +491 -0
- package/references/workflow.md +474 -0
- package/scripts/init-project-context.sh +139 -0
- package/scripts/validate-project-context.sh +164 -0
- package/templates/architecture.md +418 -0
- package/templates/design.md +654 -0
- package/templates/memory.md +368 -0
- package/templates/prd.md +320 -0
- package/templates/rules.md +619 -0
- package/templates/tasks.md +220 -0
|
@@ -0,0 +1,451 @@
|
|
|
1
|
+
# Smart Skill & MCP Delegation
|
|
2
|
+
|
|
3
|
+
> Intelligent use of other skills, MCP tools, and external capabilities.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Core Principle
|
|
8
|
+
|
|
9
|
+
**Use the right tool for the job. Delegate when specialized skills exist.**
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Skill Discovery & Usage
|
|
14
|
+
|
|
15
|
+
### Before Implementing Yourself
|
|
16
|
+
|
|
17
|
+
**Ask:**
|
|
18
|
+
1. Does a skill already exist for this?
|
|
19
|
+
2. Is there an MCP tool that handles this?
|
|
20
|
+
3. Would another AI agent do this better?
|
|
21
|
+
|
|
22
|
+
**Check:**
|
|
23
|
+
- Your AI's skills directory
|
|
24
|
+
- Available MCP servers
|
|
25
|
+
- Your AI's plugin/extension system
|
|
26
|
+
- Sub-agent capabilities
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## When to Use Other Skills
|
|
31
|
+
|
|
32
|
+
### Use Existing Skills When:
|
|
33
|
+
|
|
34
|
+
✅ **Specialized knowledge needed:**
|
|
35
|
+
- SEO optimization → SEO skill
|
|
36
|
+
- Accessibility audit → A11y skill
|
|
37
|
+
- Security review → Security skill
|
|
38
|
+
- Performance analysis → Performance skill
|
|
39
|
+
|
|
40
|
+
✅ **Complex domain:**
|
|
41
|
+
- Legal compliance → Legal skill (if available)
|
|
42
|
+
- Medical/health → Health skill (if available)
|
|
43
|
+
- Financial calculations → Finance skill (if available)
|
|
44
|
+
|
|
45
|
+
✅ **Better tooling:**
|
|
46
|
+
- Design implementation → Figma skill
|
|
47
|
+
- API documentation → OpenAPI skill
|
|
48
|
+
- Database schema → Database skill
|
|
49
|
+
|
|
50
|
+
### Don't Use Other Skills When:
|
|
51
|
+
- Simple, straightforward tasks
|
|
52
|
+
- Already have context loaded
|
|
53
|
+
- Faster to do directly
|
|
54
|
+
- No relevant skill exists
|
|
55
|
+
|
|
56
|
+
---
|
|
57
|
+
|
|
58
|
+
## MCP Server Usage
|
|
59
|
+
|
|
60
|
+
### Check Available MCP Servers
|
|
61
|
+
|
|
62
|
+
**Before starting complex tasks:**
|
|
63
|
+
```
|
|
64
|
+
Available MCP servers:
|
|
65
|
+
- context7: Library documentation lookup
|
|
66
|
+
- figma: Design implementation
|
|
67
|
+
- stripe: Payment integration
|
|
68
|
+
- aws-knowledge: AWS best practices
|
|
69
|
+
- playwright: Browser automation
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
**Use MCP when:**
|
|
73
|
+
- Need current documentation (context7)
|
|
74
|
+
- Implementing from designs (figma)
|
|
75
|
+
- Integrating third-party services (stripe, aws)
|
|
76
|
+
- Need specialized tooling (playwright)
|
|
77
|
+
|
|
78
|
+
### Recommend MCP Configuration
|
|
79
|
+
|
|
80
|
+
**If task needs unavailable MCP:**
|
|
81
|
+
```
|
|
82
|
+
This task needs [X] capability.
|
|
83
|
+
|
|
84
|
+
Recommend: Install [MCP-server-name]
|
|
85
|
+
|
|
86
|
+
Setup:
|
|
87
|
+
1. Add to your AI's MCP configuration (e.g., mcp.json):
|
|
88
|
+
{
|
|
89
|
+
"mcpServers": {
|
|
90
|
+
"server-name": {
|
|
91
|
+
"command": "uvx",
|
|
92
|
+
"args": ["package-name@latest"]
|
|
93
|
+
}
|
|
94
|
+
}
|
|
95
|
+
}
|
|
96
|
+
|
|
97
|
+
2. Restart Kiro or reconnect MCP servers
|
|
98
|
+
|
|
99
|
+
Then I can use [specific capability] to complete this efficiently.
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
---
|
|
103
|
+
|
|
104
|
+
## Kiro Powers Usage
|
|
105
|
+
|
|
106
|
+
### Check Powers Before Implementation
|
|
107
|
+
|
|
108
|
+
**For common integrations:**
|
|
109
|
+
|
|
110
|
+
| Task | Check Power | Why |
|
|
111
|
+
|------|-------------|-----|
|
|
112
|
+
| Design to code | figma power | Connect Figma → code |
|
|
113
|
+
| API docs lookup | context7 power | Current library docs |
|
|
114
|
+
| SaaS features | saas-builder power | Pre-built patterns |
|
|
115
|
+
| Payment integration | (via saas-builder) | Stripe integration |
|
|
116
|
+
| Cloud deployment | (via saas-builder) | AWS patterns |
|
|
117
|
+
|
|
118
|
+
**Usage:**
|
|
119
|
+
```
|
|
120
|
+
Task: Implement Stripe checkout
|
|
121
|
+
|
|
122
|
+
Check: saas-builder power (includes Stripe MCP)
|
|
123
|
+
Use: Built-in Stripe patterns + MCP tools
|
|
124
|
+
Result: Faster, tested, secure implementation
|
|
125
|
+
```
|
|
126
|
+
|
|
127
|
+
---
|
|
128
|
+
|
|
129
|
+
## Sub-Agent Delegation
|
|
130
|
+
|
|
131
|
+
### Use context-gatherer When:
|
|
132
|
+
- New to codebase (understand before changing)
|
|
133
|
+
- Complex feature spanning many files
|
|
134
|
+
- Investigating bugs across modules
|
|
135
|
+
- Understanding architecture patterns
|
|
136
|
+
|
|
137
|
+
**Don't use for:**
|
|
138
|
+
- Simple single-file changes
|
|
139
|
+
- Code you already understand
|
|
140
|
+
- Quick fixes
|
|
141
|
+
|
|
142
|
+
### Use general-task-execution When:
|
|
143
|
+
- Independent subtask while you work on main task
|
|
144
|
+
- Parallel work streams
|
|
145
|
+
- Well-defined isolated task
|
|
146
|
+
|
|
147
|
+
### Use documentation When:
|
|
148
|
+
- User asks about AI-specific features
|
|
149
|
+
- Questions about configuration
|
|
150
|
+
- Platform-specific documentation needed
|
|
151
|
+
|
|
152
|
+
**Never use for:**
|
|
153
|
+
- General programming questions
|
|
154
|
+
- Project-specific code issues
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
## Smart Delegation Examples
|
|
159
|
+
|
|
160
|
+
### Example 1: Design Implementation
|
|
161
|
+
|
|
162
|
+
**Scenario:** "Implement this Figma design"
|
|
163
|
+
|
|
164
|
+
**Smart approach:**
|
|
165
|
+
```
|
|
166
|
+
Checking for figma power... Found.
|
|
167
|
+
|
|
168
|
+
Using figma power:
|
|
169
|
+
- Extract design tokens
|
|
170
|
+
- Map components
|
|
171
|
+
- Generate code with design system
|
|
172
|
+
|
|
173
|
+
More accurate than manual implementation.
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
**Dumb approach:**
|
|
177
|
+
```
|
|
178
|
+
Let me manually inspect the Figma link and guess the colors...
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### Example 2: Library Documentation
|
|
182
|
+
|
|
183
|
+
**Scenario:** "How do I use Next.js App Router with authentication?"
|
|
184
|
+
|
|
185
|
+
**Smart approach:**
|
|
186
|
+
```
|
|
187
|
+
Using context7 MCP (via context7 power):
|
|
188
|
+
- Query: "Next.js App Router authentication patterns"
|
|
189
|
+
- Get current documentation
|
|
190
|
+
- Implement with latest best practices
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
**Dumb approach:**
|
|
194
|
+
```
|
|
195
|
+
Based on my training data from 2023...
|
|
196
|
+
```
|
|
197
|
+
|
|
198
|
+
### Example 3: Complex Investigation
|
|
199
|
+
|
|
200
|
+
**Scenario:** "Why is the checkout flow failing?"
|
|
201
|
+
|
|
202
|
+
**Smart approach:**
|
|
203
|
+
```
|
|
204
|
+
Delegating to context-gatherer:
|
|
205
|
+
- Investigate checkout flow end-to-end
|
|
206
|
+
- Trace data flow
|
|
207
|
+
- Identify failure points
|
|
208
|
+
|
|
209
|
+
Will implement fix after understanding root cause.
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
**Dumb approach:**
|
|
213
|
+
```
|
|
214
|
+
Let me read every file in the codebase...
|
|
215
|
+
```
|
|
216
|
+
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
## Skill Recommendation Framework
|
|
220
|
+
|
|
221
|
+
### When Task Starts
|
|
222
|
+
|
|
223
|
+
**Mental checklist:**
|
|
224
|
+
1. Is this my core competency? (code, architecture, docs)
|
|
225
|
+
2. Or specialized domain? (design, payments, cloud, SEO)
|
|
226
|
+
3. Does skill/MCP exist for specialized domain?
|
|
227
|
+
4. Would it be faster/better to use that?
|
|
228
|
+
|
|
229
|
+
### Recommendation Template
|
|
230
|
+
|
|
231
|
+
**If better tool exists:**
|
|
232
|
+
```
|
|
233
|
+
Task: [X]
|
|
234
|
+
|
|
235
|
+
Better approach: Use [skill/MCP/power]
|
|
236
|
+
|
|
237
|
+
Reason: [Why it's better]
|
|
238
|
+
|
|
239
|
+
Setup needed: [If any]
|
|
240
|
+
|
|
241
|
+
Recommend proceeding with [tool] instead of manual implementation?
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
### User Decision Point
|
|
245
|
+
|
|
246
|
+
**Let user choose:**
|
|
247
|
+
- Proceed with specialized tool (better)
|
|
248
|
+
- Proceed manually (faster if already set up)
|
|
249
|
+
|
|
250
|
+
---
|
|
251
|
+
|
|
252
|
+
## Configuration Recommendations
|
|
253
|
+
|
|
254
|
+
### Proactive Setup Suggestions
|
|
255
|
+
|
|
256
|
+
**When you notice opportunity:**
|
|
257
|
+
```
|
|
258
|
+
Note: This project could benefit from [X] MCP server.
|
|
259
|
+
|
|
260
|
+
Use case: [Specific benefit]
|
|
261
|
+
|
|
262
|
+
Setup:
|
|
263
|
+
[Exact configuration]
|
|
264
|
+
|
|
265
|
+
Worth configuring? Can improve [Y] tasks by [Z]%.
|
|
266
|
+
```
|
|
267
|
+
|
|
268
|
+
### Project-Specific Optimization
|
|
269
|
+
|
|
270
|
+
**After understanding project:**
|
|
271
|
+
```
|
|
272
|
+
Project Optimization Recommendations:
|
|
273
|
+
|
|
274
|
+
1. Figma Power: You have Figma designs
|
|
275
|
+
- Auto-sync design tokens
|
|
276
|
+
- Component generation
|
|
277
|
+
- Setup: [instructions]
|
|
278
|
+
|
|
279
|
+
2. Context7: Multiple external libraries
|
|
280
|
+
- Always current docs
|
|
281
|
+
- Faster API lookup
|
|
282
|
+
- Setup: Already available in Kiro
|
|
283
|
+
|
|
284
|
+
3. Custom Skill: [Domain-specific]
|
|
285
|
+
- Create skill for [repeated pattern]
|
|
286
|
+
- Saves time on [X] type tasks
|
|
287
|
+
```
|
|
288
|
+
|
|
289
|
+
---
|
|
290
|
+
|
|
291
|
+
## Adaptive Behavior
|
|
292
|
+
|
|
293
|
+
### Learn from Project Patterns
|
|
294
|
+
|
|
295
|
+
**If you notice:**
|
|
296
|
+
- Frequent Figma → code tasks → Recommend figma power
|
|
297
|
+
- Many API integrations → Recommend context7
|
|
298
|
+
- Repeated security audits → Recommend security skill
|
|
299
|
+
- Complex state management → Recommend architecture review skill
|
|
300
|
+
|
|
301
|
+
### Build Skill Recommendation Memory
|
|
302
|
+
|
|
303
|
+
**In memory.md:**
|
|
304
|
+
```markdown
|
|
305
|
+
## Recommended Skills/Tools
|
|
306
|
+
|
|
307
|
+
- **Figma Power:** Design implementation tasks (50% of UI work)
|
|
308
|
+
- **Context7:** Library docs lookup (saves ~5 min per lookup)
|
|
309
|
+
- **Custom SEO Skill:** Frequent SEO audits needed
|
|
310
|
+
|
|
311
|
+
## MCP Servers to Configure
|
|
312
|
+
|
|
313
|
+
- [ ] Stripe MCP: Payment features planned (Phase 2)
|
|
314
|
+
- [ ] AWS Knowledge: Deployment optimization needed
|
|
315
|
+
```
|
|
316
|
+
|
|
317
|
+
---
|
|
318
|
+
|
|
319
|
+
## Token Efficiency with Delegation
|
|
320
|
+
|
|
321
|
+
### Delegation Saves Tokens
|
|
322
|
+
|
|
323
|
+
**Example: Design implementation**
|
|
324
|
+
|
|
325
|
+
**Manual (High Tokens):**
|
|
326
|
+
- Read design.md thoroughly
|
|
327
|
+
- Inspect existing components
|
|
328
|
+
- Extract colors, spacing, patterns manually
|
|
329
|
+
- Implement component
|
|
330
|
+
- Verify against design
|
|
331
|
+
- **Tokens:** ~2000
|
|
332
|
+
|
|
333
|
+
**Delegated (Low Tokens):**
|
|
334
|
+
- Use figma power
|
|
335
|
+
- Extract design automatically
|
|
336
|
+
- Generate component
|
|
337
|
+
- Review output
|
|
338
|
+
- **Tokens:** ~300
|
|
339
|
+
|
|
340
|
+
### When Delegation Costs More
|
|
341
|
+
|
|
342
|
+
**Don't delegate if:**
|
|
343
|
+
- Setup time > implementation time
|
|
344
|
+
- Simple task (< 5 min)
|
|
345
|
+
- Already have full context
|
|
346
|
+
- No suitable tool exists
|
|
347
|
+
|
|
348
|
+
---
|
|
349
|
+
|
|
350
|
+
## Smart Tool Selection Matrix
|
|
351
|
+
|
|
352
|
+
| Task Type | Primary Tool | Fallback | Skip Delegation |
|
|
353
|
+
|-----------|--------------|----------|-----------------|
|
|
354
|
+
| Code changes | Direct implementation | - | Always do directly |
|
|
355
|
+
| Design → Code | Figma power | Manual | If no Figma file |
|
|
356
|
+
| Library docs | Context7 MCP | Web search | If simple/known |
|
|
357
|
+
| Architecture investigation | context-gatherer | Manual inspection | If < 3 files |
|
|
358
|
+
| SEO audit | SEO skill | Manual checklist | If not applicable |
|
|
359
|
+
| Security audit | Security skill | Manual review | For tiny changes |
|
|
360
|
+
| Payment integration | Stripe MCP | Manual API | If simple endpoint |
|
|
361
|
+
| Complex investigation | context-gatherer | Read files | If already know area |
|
|
362
|
+
|
|
363
|
+
---
|
|
364
|
+
|
|
365
|
+
## Efficiency Decision Tree
|
|
366
|
+
|
|
367
|
+
```
|
|
368
|
+
New Task
|
|
369
|
+
↓
|
|
370
|
+
Is it core coding task?
|
|
371
|
+
YES → Do it directly
|
|
372
|
+
NO ↓
|
|
373
|
+
|
|
374
|
+
Is there specialized skill/MCP?
|
|
375
|
+
NO → Do it manually
|
|
376
|
+
YES ↓
|
|
377
|
+
|
|
378
|
+
Is tool already configured?
|
|
379
|
+
YES → Use tool (faster + better)
|
|
380
|
+
NO ↓
|
|
381
|
+
|
|
382
|
+
Is setup time < task time?
|
|
383
|
+
YES → Recommend setup → Use tool
|
|
384
|
+
NO → Do manually, note for future
|
|
385
|
+
```
|
|
386
|
+
|
|
387
|
+
---
|
|
388
|
+
|
|
389
|
+
## Communication: Tool Recommendations
|
|
390
|
+
|
|
391
|
+
### Concise Format
|
|
392
|
+
|
|
393
|
+
**When recommending tool:**
|
|
394
|
+
```
|
|
395
|
+
Better tool exists: [name]
|
|
396
|
+
|
|
397
|
+
Benefit: [X] faster, [Y] more accurate
|
|
398
|
+
|
|
399
|
+
Setup: [Quick instructions or "already available"]
|
|
400
|
+
|
|
401
|
+
Use it? [Y/n]
|
|
402
|
+
```
|
|
403
|
+
|
|
404
|
+
**Caveman mode:**
|
|
405
|
+
```
|
|
406
|
+
[Tool name] better for this.
|
|
407
|
+
Setup: [1 line]
|
|
408
|
+
Use?
|
|
409
|
+
```
|
|
410
|
+
|
|
411
|
+
---
|
|
412
|
+
|
|
413
|
+
## Self-Awareness: Know Your Limits
|
|
414
|
+
|
|
415
|
+
### You're Best At:
|
|
416
|
+
- Writing code
|
|
417
|
+
- Following patterns
|
|
418
|
+
- Maintaining consistency
|
|
419
|
+
- Implementing requirements
|
|
420
|
+
- Refactoring
|
|
421
|
+
- Documentation
|
|
422
|
+
|
|
423
|
+
### You're Not Best At:
|
|
424
|
+
- Current library docs (use context7)
|
|
425
|
+
- Design precision (use figma power)
|
|
426
|
+
- Deep architecture investigation (use context-gatherer)
|
|
427
|
+
- Specialized domains (use domain skills)
|
|
428
|
+
|
|
429
|
+
**Be honest:** Recommend better tools when they exist.
|
|
430
|
+
|
|
431
|
+
---
|
|
432
|
+
|
|
433
|
+
## Summary
|
|
434
|
+
|
|
435
|
+
**Smart AI behavior:**
|
|
436
|
+
|
|
437
|
+
1. **Check available skills/MCP before implementing**
|
|
438
|
+
2. **Delegate specialized tasks to specialized tools**
|
|
439
|
+
3. **Recommend configuration for repeated patterns**
|
|
440
|
+
4. **Be token-efficient: delegation often saves tokens**
|
|
441
|
+
5. **Know your strengths: code well, delegate smartly**
|
|
442
|
+
|
|
443
|
+
**Dumb AI behavior:**
|
|
444
|
+
|
|
445
|
+
1. Do everything manually
|
|
446
|
+
2. Ignore available tools
|
|
447
|
+
3. Never recommend optimization
|
|
448
|
+
4. Waste tokens on duplicate work
|
|
449
|
+
5. Pretend to know everything
|
|
450
|
+
|
|
451
|
+
**Goal:** Use right tool for each job. Maximize efficiency. Deliver better results faster.
|