using-superpowers

using-superpowers - Claude Code Skill Usage Guide

Skill Overview

using-superpowers is Claude Code’s foundational skill, used to establish how to look up and use the skill system. This skill requires that, at the start of any conversation, you check the relevant skills first—even if there’s only a 1% chance that a skill might apply.

When to Use It

1. Starting a New Conversation or Session

Every time you begin a new conversation or task, you must first check whether any relevant skills are available. This skill applies to all Claude Code users and ensures that you don’t miss potentially relevant professional skills before doing anything.

2. When the Direction of a Task Is Unclear

When you’re unsure how to handle a task, or there are multiple possible approaches, using this skill helps you find the right guidance skill. Professional skills will tell you how to correctly explore the codebase, design a plan, or execute a specific task.

3. When Multiple Skills Might Apply

When faced with multiple optional skills, this skill provides prioritization rules: processing-type skills (e.g., brainstorming, debugging) take precedence over implementation-type skills (e.g., frontend-design). This helps you choose the correct execution order.

Core Capabilities

1% Rule and Mandatory Invocation Mechanism

The key principle of this skill is: “As long as you think there’s a 1% chance that a skill might apply, you must call it.” This is not optional, and you can’t rationalize your way out of it. Even if the task looks simple, or you feel you can solve it quickly, you still need to check for any relevant skills first.

Red-Flag Detection System

The skill includes a detailed list of red flags to help you identify psychological patterns of rationalization/avoidance. Thoughts such as “This is just a simple problem,” “I need to gather information first,” “I can quickly check the files,” and so on are warning signs. They remind you to pause and call the skill first.

Skill Priority Management

When multiple skills might apply, this skill clearly defines the selection order: processing-type skills come before implementation-type skills. For example, “building a feature” should first use the brainstorming skill, and then use the specific implementation skill. This ensures you have sufficient thinking and planning before you start writing code.

Frequently Asked Questions

What Is the 1% Rule?

The 1% rule means: if you think there’s a 1% chance that some skill could apply to the current task, you must call that skill. This is not optional, and it doesn’t allow you to rationalize your way out. Even if the task looks simple, or you think you can solve it quickly, you still need to check the skill list first.

Do Simple Problems Also Require Using Skills?

Yes. The skill system states clearly that “simple things can also become complex.” Using skills helps prevent small issues from turning into big problems. Even if a task looks straightforward, there may be relevant professional skills that provide better methods and guidance.

What If After Calling a Skill It Turns Out Not to Apply?

No problem. The skill documentation explicitly states: “If the skill you called later turns out not to be applicable in this situation, you don’t need to use it.” Calling a skill is for checking—not a commitment that you must use it. It’s better to check more than to miss professional guidance that could change how you work.