Advanced tools and superpowers for power users
Showing 37 skills
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Guides completion of development work by presenting clear options and handling chosen workflow.
Implement multi-layered testing and security best practices.
Core skills library for Claude Code with 20+ battle-tested skills including TDD, debugging, and collaboration patterns
Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.
Develop and document capabilities
Create and manage command structures
Manage conditional pauses or delays
Validate work before finalizing
Manage multiple Git working trees
Process and incorporate code feedback
Initiate code review processes
Complete Git code branches
Identify ineffective testing practices
Collaborative testing approaches
Investigate and identify fundamental problems
Methodical problem-solving in code
Development using multiple sub-agents
Write tests before implementing code
Leverage core platform capabilities
Distribute and communicate capabilities
Coordinate multiple simultaneous agents
Implement and run strategic plans
Create strategic documentation
Generate and explore ideas
Use when implementing any feature or bugfix, before writing implementation code.
Use when errors occur deep in execution and you need to trace back to find the original trigger.
Multi-layered security approaches
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when you have a spec or requirements for a multi-step task, before touching code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation