aile-using-superpowers

If a skill applies, youhave no choice, and must use it.

This is not a suggestion, but a hard rule. Do not start working and then add the skill afterward.

How to obtain skills

In Claude Code: Use theSkilltool. When you invoke a skill, its contents will be loaded and presented to you - follow it directly. Never use the read tool on skill files.

In other environments: Check your platform documentation to learn how to load skills.

Usage tips

Rules

Before any response or action, first invoke the relevant skill or the skill explicitly requested by name.
Even if a skill is only 1% likely to apply, invoke it to check first.
If after invoking it you confirm it does not apply, you may not use it; but you cannot skip the invocation step.

digraph skill_flow {
    "User message received" [shape=doublecircle];
    "Might any skill apply?" [shape=diamond];
    "Invoke Skill tool" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create TodoWrite todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create TodoWrite todo per item" -> "Follow skill exactly";
}

Red flags

These thoughts mean stop - you are rationalizing:

Thought	Reality
"This is just a simple question"	The question is the task. Check the skill.
"I need more context first"	The skill check comes before clarifying questions.
"Let me explore the codebase first"	The skill tells you how to explore. Check it first.
"I can quickly check git/files"	Files lack contextual context. Check the skill.
"Let me gather information first"	The skill tells you how to gather information.
"This does not require a formal skill"	If a skill exists, use it.
"I remember this skill"	Skills keep evolving. Read the current version.
"This does not count as a task"	Action = task. Check the skill.
"The skill is overkill"	Simple things become complicated. Use it.
"I will do one thing first"	Check before doing anything.
"This feels productive"	Undisciplined action wastes time. Skills prevent this from happening.
"I know what this means"	Understanding the concept ≠ using the skill. Invoke it.

Skill priority

When multiple skills can be applied, use the following order:

1. Process skills first(brainstorming, debugging) - these determine how to handle the task
2. Implementation skills second(frontend design, mcp-builder) - these guide execution

"Let's X right now" → brainstorm first, then implementation skills. "Fix this bug" → debug first, then domain-specific skills.

Skill types

Rigid(TDD, debugging): follow strictly. Do not adapt the discipline.

Flexible(patterns): adapt the principles according to the specific situation.

The skill itself will tell you which one.

User instructions

The description says "what to do", not "how to do it". "Add X" or "Fix Y" does not mean skipping the workflow.