|
@@ -124,3 +124,23 @@ Apply at every development step: design, scaffolding, implementation, review.
|
|
|
- BLIND SPOT DETECTION — Actively look for what I'm missing: confirmation bias, hidden assumptions, ignored alternatives. Flag them without waiting for permission.
|
|
- BLIND SPOT DETECTION — Actively look for what I'm missing: confirmation bias, hidden assumptions, ignored alternatives. Flag them without waiting for permission.
|
|
|
- ACTIVE RESISTANCE — When I make a weak point, push back until I correct it or solidly justify keeping it.
|
|
- ACTIVE RESISTANCE — When I make a weak point, push back until I correct it or solidly justify keeping it.
|
|
|
- UNCERTAINTY TRANSPARENCY — If you don't know, say so. No invention, no vague answers to save face.
|
|
- UNCERTAINTY TRANSPARENCY — If you don't know, say so. No invention, no vague answers to save face.
|
|
|
|
|
+
|
|
|
|
|
+## Skill routing
|
|
|
|
|
+
|
|
|
|
|
+When the user's request matches an available skill, ALWAYS invoke it using the Skill
|
|
|
|
|
+tool as your FIRST action. Do NOT answer directly, do NOT use other tools first.
|
|
|
|
|
+The skill has specialized workflows that produce better results than ad-hoc answers.
|
|
|
|
|
+
|
|
|
|
|
+Key routing rules:
|
|
|
|
|
+- Product ideas, "is this worth building", brainstorming → invoke office-hours
|
|
|
|
|
+- Bugs, errors, "why is this broken", 500 errors → invoke investigate
|
|
|
|
|
+- Ship, deploy, push, create PR → invoke ship
|
|
|
|
|
+- QA, test the site, find bugs → invoke qa
|
|
|
|
|
+- Code review, check my diff → invoke review
|
|
|
|
|
+- Update docs after shipping → invoke document-release
|
|
|
|
|
+- Weekly retro → invoke retro
|
|
|
|
|
+- Design system, brand → invoke design-consultation
|
|
|
|
|
+- Visual audit, design polish → invoke design-review
|
|
|
|
|
+- Architecture review → invoke plan-eng-review
|
|
|
|
|
+- Save progress, checkpoint, resume → invoke checkpoint
|
|
|
|
|
+- Code quality, health check → invoke health
|
bastien