Plugin superpowers
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Como instalar o plugin superpowers
Execute os dois comandos dentro do Claude Code. O primeiro adiciona o marketplace uma vez; o segundo instala o plugin.
/plugin marketplace add pickleshell/next-level-agent
/plugin install superpowers@superpowers-devO que há dentro de superpowers
19 partes lidas dos próprios arquivos do plugin.
Skills 18
Claude o carrega quando a tarefa coincide- assistant-notebook
Consult and maintain the user's persistent Assistant Notebook in ChatGPT Library or on the local filesystem as a secondary recall aid and index. The current conversation and other available context are primary and usually more complete. Consult it once when starting a substantive working context or restoring continuity, then reuse the recovered context without rereading the notebook on every request. Reconsult only when needed for a missing fact, older decision, project switch, or context loss. Update it after meaningful progress with verified outcomes, decisions, files, blockers, and next steps.
- 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
- executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
- finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
- mem0-memory
Use optional Mem0 memory tools for focused cross-session recall and short verified durable facts. Use when the user asks to remember or forget something, when resuming work that may need prior context, or after verified progress creates a stable fact worth retaining.
- next-level-agent
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
- planning-parallel-work
Use when a substantial software task needs decomposition into dependency-aware, independently verifiable work items and safe parallel execution groups before implementation begins.
- 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
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
- systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- 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
- 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
- writing-acceptance-tests
Use when independent tests must be derived from a specification, public interface, or acceptance criteria before implementation, without writing or relying on production code.
- writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
- writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Hooks 1
Executa nestes eventos- SessionStartcommand
startup|clear|compact
Usando superpowers no Claude Code
Skills não precisam de comando. Claude as lê quando sua solicitação corresponde ao que elas descrevem.
Atualizar, desligar ou remover
- Atualizar o plugin (shell)
- claude plugin update superpowers@superpowers-dev
- Atualizar o marketplace
- /plugin marketplace update superpowers-dev
- Desligar por enquanto
- /plugin disable superpowers@superpowers-dev
- Remover
- /plugin uninstall superpowers@superpowers-dev
Skills em superpowers
- assistant-notebookpickleshell/next-level-agent
Consult and maintain the user's persistent Assistant Notebook in ChatGPT Library or on the local filesystem as a secondary recall aid and index. The current conversation and other available context are primary and usually more complete. Consult it once when starting a substantive working context or restoring continuity, then reuse the recovered context without rereading the notebook on every request. Reconsult only when needed for a missing fact, older decision, project switch, or context loss. Update it after meaningful progress with verified outcomes, decisions, files, blockers, and next steps.
4 arquivos7estrelas - brainstormingpickleshell/next-level-agent
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.
8 arquivos7estrelas - next-level-agentpickleshell/next-level-agent
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
6 arquivos7estrelas - requesting-code-reviewpickleshell/next-level-agent
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
2 arquivos7estrelas - subagent-driven-developmentpickleshell/next-level-agent
Use when executing implementation plans with independent tasks in the current session
7 arquivos7estrelas - systematic-debuggingpickleshell/next-level-agent
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
11 arquivos7estrelas - test-driven-developmentpickleshell/next-level-agent
Use when implementing any feature or bugfix, before writing implementation code
2 arquivos7estrelas - writing-planspickleshell/next-level-agent
Use when you have a spec or requirements for a multi-step task, before touching code
2 arquivos7estrelas - writing-skillspickleshell/next-level-agent
Use when creating new skills, editing existing skills, or verifying skills work before deployment
7 arquivos7estrelas - dispatching-parallel-agentspickleshell/next-level-agent
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
7estrelas - executing-planspickleshell/next-level-agent
Use when you have a written implementation plan to execute in a separate session with review checkpoints
7estrelas - finishing-a-development-branchpickleshell/next-level-agent
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
7estrelas - mem0-memorypickleshell/next-level-agent
Use optional Mem0 memory tools for focused cross-session recall and short verified durable facts. Use when the user asks to remember or forget something, when resuming work that may need prior context, or after verified progress creates a stable fact worth retaining.
7estrelas - planning-parallel-workpickleshell/next-level-agent
Use when a substantial software task needs decomposition into dependency-aware, independently verifiable work items and safe parallel execution groups before implementation begins.
7estrelas - receiving-code-reviewpickleshell/next-level-agent
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
7estrelas - using-git-worktreespickleshell/next-level-agent
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
7estrelas - verification-before-completionpickleshell/next-level-agent
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
7estrelas - writing-acceptance-testspickleshell/next-level-agent
Use when independent tests must be derived from a specification, public interface, or acceptance criteria before implementation, without writing or relying on production code.
7estrelas
Perguntas sobre o plugin superpowers
Como instalo o plugin superpowers?
No Claude Code, execute /plugin marketplace add pickleshell/next-level-agent e depois /plugin install superpowers@superpowers-dev.
O que o plugin superpowers inclui?
superpowers agrupa 18 skills, hooks.
Como eu atualizo ou removo o plugin superpowers?
Atualize-o com claude plugin update superpowers@superpowers-dev no seu shell, ou pela aba Instalados de /plugin. Remova-o com /plugin uninstall superpowers@superpowers-dev.
Sob qual licença o plugin superpowers está?
MIT, conforme declarado no manifesto do plugin.