
using-superpowers
by yairbederman
SKILL.md
name: using-superpowers description: Use at conversation start - establishes how to find and use skills, requiring skill loading before ANY response
Using Skills
The Rule
Load and apply relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you should check. If a skill turns out to be wrong for the situation, you don't need to use it.
How to Access Skills
Skills are located in global_workflows/skills/. Each skill folder contains a SKILL.md file with:
- YAML frontmatter:
nameanddescription - Detailed instructions for when and how to apply the skill
To use a skill:
- Read the
SKILL.mdfile - Announce: "Applying [skill-name] skill for [purpose]."
- Follow the skill instructions exactly
Mode-Based Auto-Loading
Skills are automatically applicable based on the current Engineering Agent mode:
| Agent Mode | Applicable Skills |
|---|---|
| ProductSpecReview | brainstorming |
| FeaturePlanning | brainstorming, writing-plans |
| TechSpec | writing-plans |
| TaskPlanning | writing-plans |
| Implementation | test-driven-development, executing-plans |
| BugFix | test-driven-development |
| CodeReview | requesting-code-review |
Common Rationalizations (Don't Fall For These)
| Rationalization | Reality |
|---|---|
| "I already know TDD" | Skills have specific checklists. Read them. |
| "This is quick, no skill needed" | Simple things become complex. Use the skill. |
| "I'll check the skill later" | Check BEFORE doing anything. |
| "The skill is overkill" | Discipline prevents mistakes. |
Skill Types
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (brainstorming, writing-plans): Adapt principles to context.
The skill itself tells you which type it is.
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon