Superpowers supports multiple activation modes to fit your workflow.
Superpowers activates on every session. Maximum automation.
# .superpowers/config.yaml
activation:
mode: alwaysSuperpowers only activates when explicitly enabled.
activation:
mode: opt-inThen create the enable marker:
touch .superpowers/enabledSuperpowers activates unless explicitly disabled.
activation:
mode: opt-outTo disable for a specific project:
touch .superpowers/disabledSuperpowers never activates (but remains installed).
activation:
mode: neverControl how much of Superpowers loads:
Complete workflow: brainstorming, TDD, subagent-driven-development, etc.
activation:
level: fullOnly core skills: brainstorming, using-superpowers.
activation:
level: lightweightOnly using-superpowers skill.
activation:
level: minimalSuperpowers can adapt based on git context:
activation:
context_aware:
# Don't activate when on main/master branch
disable_on_main_branch: true
# Use lightweight mode in detached HEAD
lightweight_on_detached_head: true
# Only activate in git repositories
require_git_repo: trueFine-grained control over individual skills:
skills:
brainstorming:
enabled: true
auto_trigger: true
test-driven-development:
enabled: true
enforce_red_green_refactor: true
dispatching-parallel-agents:
enabled: false # Disable advanced featureQuick toggle without editing config:
# Disable for this session
export SUPERPOWERS_MODE=disabled
# Force enable
export SUPERPOWERS_MODE=enabledIn Claude Code, use these commands:
/superpowers on- Enable for this project/superpowers off- Disable for this project/superpowers level full|lightweight|minimal- Change activation level/superpowers status- Show current configuration
If you have custom skills in ~/.config/superpowers/skills, move them:
mkdir -p ~/.claude/skills
mv ~/.config/superpowers/skills/* ~/.claude/skills/
rmdir ~/.config/superpowers/skillsThis removes the migration warning from startup.