The directory for
Claude Code skills
Stop hunting across scattered repos. Search by task and install the best prompts and orchestrators in one command.
Find the right skill for the task
Community-built prompts and orchestrators, organised around the work you need Claude Code to do.
Receiving Code Review
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
Executing Plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Dispatching Parallel Agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Requesting Code Review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Writing Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Using Superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session
Test Driven Development
Use when implementing any feature or bugfix, before writing implementation code
Using Git Worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Finishing A Development Branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Verification Before Completion
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
One path from task to working skill
Spellbook replaces repo hunting with a repeatable flow: search in the language of the job, inspect the skill, then install it.
npx skills add spellbook/<skill>Describe the task, not the package name.
Review the prompt, author, and intended trigger.
Bring the skill into your workflow in one command.