From f198f1e7d95fb6e913207b3d7bfde6ac4935f5bf Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Thu, 21 May 2026 14:16:08 -0700 Subject: [PATCH] @mhat reported that his claude got confused about 'debugging' being named as a skill in the bootstrap --- skills/using-superpowers/SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/skills/using-superpowers/SKILL.md b/skills/using-superpowers/SKILL.md index c4c9d545..e9294781 100644 --- a/skills/using-superpowers/SKILL.md +++ b/skills/using-superpowers/SKILL.md @@ -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.