using-superpowers

Use when starting any conversation. Establishes how to find and use skills, requiring skill invocation before any response.

509 stars

Best use case

using-superpowers is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when starting any conversation. Establishes how to find and use skills, requiring skill invocation before any response.

Teams using using-superpowers should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/using-superpowers/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/superpowers/skills/using-superpowers/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/using-superpowers/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How using-superpowers Compares

Feature / Agentusing-superpowersStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when starting any conversation. Establishes how to find and use skills, requiring skill invocation before any response.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Using Superpowers

## Overview

Invoke relevant skills BEFORE any response or action. Even a 1% chance means invoke the skill.

## The Rule

Check for applicable skills before any task. Skills are mandatory workflows, not suggestions.

## Skill Priority

1. **Process skills first** (brainstorming, debugging) - determine HOW to approach
2. **Implementation skills second** - guide execution

## Skill Types

- **Rigid** (TDD, debugging) - Follow exactly
- **Flexible** (patterns) - Adapt principles to context

## Red Flags

- "This is just a simple question" - questions are tasks, check for skills
- "I need more context first" - skill check comes BEFORE clarifying questions
- "The skill is overkill" - simple things become complex, use it

## Tool Use

Meta-skill for the overall methodology. Ensures skills are always checked and invoked.