Give Claude Code superpowers with a comprehensive skills library of proven techniques, patterns, and tools.
- Testing Skills - TDD, async testing, anti-patterns
- Debugging Skills - Systematic debugging, root cause tracing, verification
- Collaboration Skills - Brainstorming, planning, code review, parallel agents
- Meta Skills - Creating, testing, and contributing skills
Plus:
- Slash Commands -
/brainstorm
,/write-plan
,/execute-plan
- Skills Search - Grep-powered discovery of relevant skills
- Gap Tracking - Failed searches logged for skill creation
Read the introduction: Superpowers for Claude Code
# In Claude Code
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace
That's it! On first session, the plugin automatically:
- Sets up
~/.config/superpowers/
as your personal skills repository - Initializes git repo for version control
- Makes core skills searchable alongside your personal skills
- Adds
/brainstorm
,/write-plan
, and/execute-plan
commands - Offers to create public GitHub repo for sharing your skills
# Check that commands appear
/help
# Should see:
# /brainstorm - Interactive design refinement
# /write-plan - Create implementation plan
# /execute-plan - Execute plan in batches
Write your own skills to ~/.config/superpowers/skills/
:
- All personal skills automatically discovered by search tools
- Personal skills shadow core skills when names match
- Version controlled with git
- Optional: Share on GitHub and contribute back to core
See skills/meta/writing-skills
for how to create new skills.
See skills/meta/sharing-skills
for how to contribute to core.
Find both personal and core skills before starting any task:
${CLAUDE_PLUGIN_ROOT}/scripts/find-skills # All skills with descriptions
${CLAUDE_PLUGIN_ROOT}/scripts/find-skills test # Filter by pattern
${CLAUDE_PLUGIN_ROOT}/scripts/find-skills 'TDD|debug' # Regex pattern
Brainstorm a design:
/brainstorm
Create an implementation plan:
/write-plan
Execute the plan:
/execute-plan
Testing (skills/testing/
)
- test-driven-development - RED-GREEN-REFACTOR cycle
- condition-based-waiting - Async test patterns
- testing-anti-patterns - Common pitfalls to avoid
Debugging (skills/debugging/
)
- systematic-debugging - 4-phase root cause process
- root-cause-tracing - Find the real problem
- verification-before-completion - Ensure it's actually fixed
- defense-in-depth - Multiple validation layers
Collaboration (skills/collaboration/
)
- brainstorming - Socratic design refinement
- writing-plans - Detailed implementation plans
- executing-plans - Batch execution with checkpoints
- dispatching-parallel-agents - Concurrent subagent workflows
- remembering-conversations - Search past work
- using-git-worktrees - Parallel development branches
- requesting-code-review - Pre-review checklist
- receiving-code-review - Responding to feedback
Meta (skills/meta/
)
- setting-up-personal-superpowers - Personal skills repository setup
- writing-skills - TDD for documentation, create new skills
- sharing-skills - Contribute skills back to core
- testing-skills-with-subagents - Validate skill quality
- gardening-skills-wiki - Maintain and improve skills
- brainstorm.md - Interactive design refinement using Socratic method
- write-plan.md - Create detailed implementation plans
- execute-plan.md - Execute plans in batches with review checkpoints
In scripts/
directory:
- find-skills - Unified skill discovery with descriptions (replaces list-skills + skills-search)
- skill-run - Generic runner for any skill script (searches personal then core)
Skill-specific tools:
- search-conversations - Semantic search of past Claude sessions (in remembering-conversations skill)
Using scripts:
${CLAUDE_PLUGIN_ROOT}/scripts/find-skills # Show all skills
${CLAUDE_PLUGIN_ROOT}/scripts/find-skills pattern # Search skills
${CLAUDE_PLUGIN_ROOT}/scripts/skill-run <path> [args] # Run any skill script
- SessionStart Hook - Auto-setup personal skills repo, inject core skills context
- Two-Tier Skills - Personal skills (
~/.config/superpowers/skills/
) + Core skills (plugin) - Skills Discovery -
find-skills
searches both locations with descriptions - Shadowing - Personal skills override core skills when paths match
- Mandatory Workflow - Skills become required when they exist for your task
- Gap Tracking - Failed searches logged to
~/.config/superpowers/search-log.jsonl
- Test-Driven Development - Write tests first, always
- Systematic over ad-hoc - Process over guessing
- Complexity reduction - Simplicity as primary goal
- Evidence over claims - Verify before declaring success
- Domain over implementation - Work at problem level, not solution level
The plugin auto-creates your personal superpowers directory on first session.
Default location: ~/.config/superpowers/
Customize via environment variables:
# Option 1: Set exact location
export PERSONAL_SUPERPOWERS_DIR="$HOME/my-superpowers"
# Option 2: Use XDG standard
export XDG_CONFIG_HOME="$HOME/.local/config" # Uses $HOME/.local/config/superpowers
Structure:
~/.config/superpowers/ # (or your custom location)
├── .git/ # Git repository
├── .gitignore # Ignores logs and indexes
├── README.md # About your personal superpowers
├── skills/ # Your personal skills
│ └── your-skill/
│ └── SKILL.md
├── search-log.jsonl # Failed skill searches (not tracked)
└── conversation-index/ # Indexed conversations (not tracked)
Why git? Track your skills evolution, share with others, contribute back to core.
Write personal skills:
- Create in
~/.config/superpowers/skills/your-skill/
- Follow TDD process in
skills/meta/writing-skills
- Commit to your personal repo
Share with everyone:
- Follow workflow in
skills/meta/sharing-skills
- Fork → Branch → Copy → PR to core
- Keep personal version or delete after merge
Missing a skill? Edit skills/REQUESTS.md
or open an issue
MIT License - see LICENSE file for details