brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
THE SKILLS DIRECTORY
Explore all skills.
One skill. A whole new possibility. Find your next workflow.
systematic-debugging
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
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
writing-plans
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
diagnosing-superpowers
diagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path,…
finishing-a-development-branch
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-review
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
requesting-code-review
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
using-superpowers
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
ask-matt
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
diagnosing-bugs
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
domain-modeling
domain-modeling
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
git-guardrails-claude-code
git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
grilling
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
implement-spec
implement-spec
Implement the result of /to-spec and /to-tickets in code.
setup-matt-pocock-skills
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
18 / 5514
Direct from public GitHub repositories
An independently imported catalog with original authors, licenses and source links. Classification is not a security audit.
Sources and import coverage