If you've spent any time in the Claude Code plugin marketplace, you've seen both superpowers and myclaude sitting near the top of the list. Both are verified. Both bundle more than ten skills. Both aim to upgrade Claude Code from "smart autocomplete" to "disciplined collaborator." But they take different routes, and the right choice depends on what you actually want out of the tool.

The headline numbers

  • Superpowers — 14 skills, 162,164 stars. The heavyweight.
  • myclaude — 14 skills, 2,606 stars. A smaller, more opinionated package.

Stars are a rough popularity signal, not a quality one. Both plugins ship real, well-maintained code.

Philosophy

Superpowers is built around process. The skill names give it away: systematic-debugging, test-driven-development, verification-before-completion, writing-plans, executing-plans, requesting-code-review. It tries to impose engineering discipline on every session — hypothesis-first debugging, spec-before-code, evidence-before-claims. It's heavy in the best way. If you've ever watched Claude confidently claim "fixed!" without running the tests, superpowers is what fixes that.

myclaude is built around composable building blocks — the skills lean more toward utilities (omo, test-cases) than meta-methodology. It's lighter-touch. It assumes you already know how you want to work and just want good tools for the individual steps.

Where they overlap

Both have test-oriented skills. Both encourage structured thinking. Both include some form of plan-before-execute flow. You don't need both unless you're curating.

Where they diverge

Superpowers has parallel-agent dispatching (dispatching-parallel-agents) and worktree orchestration (using-git-worktrees) that myclaude doesn't match. If you work in a setup where Claude is spawning subagents against isolated worktrees, superpowers is a clear win.

myclaude is lighter to adopt. Superpowers can feel heavy the first week — there's a lot of "I should be using a subagent for this" internal friction. myclaude doesn't impose that load. If you want a few good skills without a philosophy, it's the better choice.

Which should you install?

Install superpowers if: you're building non-trivial software, working in a codebase where bugs are expensive, or you already feel like Claude moves too fast and skips steps. The process skills are the value.

Install myclaude if: you want utility over discipline, or you're still figuring out your workflow and don't want a prescriptive framework.

Install both: plugins compose, skills don't clash. Many users run both and pull the subset they actually use from each.

A note on maturity

Superpowers sees more frequent updates — last commit within the past few days at time of writing, versus about ten days for myclaude. Both are actively maintained, but superpowers moves faster. For production setups where you want stability, that can cut either way.

Bottom line

If you can only install one, pick superpowers. The meta-skills (systematic-debugging, verification-before-completion) are genuinely the best-in-class examples of what the Claude Code plugin system can do. See the plugin page for the exact install command and the full skill list.