|
|
@@ -102,15 +102,15 @@ These thoughts mean STOP—you're rationalizing:
|
|
|
|
|
|
When multiple skills could apply, use this order:
|
|
|
|
|
|
-1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
|
|
|
+1. **Process skills first** (brainstorming, systematic-debugging) - these determine HOW to approach the task
|
|
|
2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution
|
|
|
|
|
|
"Let's build X" → brainstorming first, then implementation skills.
|
|
|
-"Fix this bug" → debugging first, then domain-specific skills.
|
|
|
+"Fix this bug" → systematic-debugging first, then domain-specific skills.
|
|
|
|
|
|
## Skill Types
|
|
|
|
|
|
-**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.
|
|
|
+**Rigid** (TDD, systematic-debugging): Follow exactly. Don't adapt away discipline.
|
|
|
|
|
|
**Flexible** (patterns): Adapt principles to context.
|
|
|
|