Claude Code plugins are the “install my whole setup at once” feature. Instead of adding slash commands, a subagent, a couple of skills, and an MCP server by hand, a plugin bundles them into one package you install from a marketplace. That’s genuinely useful — and it’s also why the plugin ecosystem ballooned quickly and got noisy.
This is an honest take on plugins in 2026: what they actually are, which ones are worth checking first, where to install them, and why each one earns its spot. It is not a universal “install all of these” ranking. The best plugin set is the small set that matches your stack.
If plugins, skills, and MCP blur together for you, read plugins vs skills vs MCP first — it untangles the layers.
What a plugin actually bundles
A plugin can include any mix of Claude Code’s extension points:
What's inside a plugin
| Slash commands | Reusable prompts you trigger by name |
|---|---|
| Subagents | Specialized helpers with their own prompts and tools |
| Skills | On-demand procedures and conventions |
| Hooks | Commands that run on agent events |
| MCP servers | Connections to external systems |
That bundling is the point and the catch. A plugin that adds a well-scoped subagent and two commands is cheap and useful. A plugin that quietly connects four MCP servers carries the full context cost of those servers every session. So “what does this plugin include” is the first question, always.
The honest state of the ecosystem
The official directory and community catalog are now big enough that browsing them without a filter is a time sink. There are excellent plugins in there, but also narrow experiments and wrappers you do not need. Volume is not a signal of value here.
The plugins worth checking first
Use this as a shortlist, not a shopping cart. Pick the rows that match your daily work, install one or two, then come back when you feel a real missing capability.
2026 shortlist
The plugins worth checking first
16 practical picks
github
Teams that live in GitHub issues, pull requests, and repository search.
Install
/plugin install github@claude-plugins-official Download / source
Why it is best: It removes a lot of copy-paste from normal coding work. Claude can inspect issue context, PR context, repo metadata, and review material without you manually dragging everything into the chat.
typescript-lsp
TypeScript projects where diagnostics, definitions, and symbol navigation matter.
Install
/plugin install typescript-lsp@claude-plugins-official Download / source
Why it is best: A real language server gives Claude better signals than grep alone: type errors, references, definitions, and project-aware navigation. That is especially valuable in large frontend and Node.js codebases.
Use the LSP plugin for your actual stack: pyright-lsp for Python, gopls-lsp for Go, or rust-analyzer-lsp for Rust.
playwright
Frontend work where the final answer depends on what actually renders in the browser.
Install
/plugin install playwright@claude-plugins-official Download / source
Why it is best: It lets Claude verify UI changes with screenshots, interactions, and rendered page state instead of guessing from component code. For visual bugs, that is a major upgrade.
frontend-design
Projects where you want Claude to build interface work that feels less generic.
Install
/plugin install frontend-design@claude-plugins-official Download / source
Why it is best: It packages frontend design judgment as a reusable workflow, so Claude pays more attention to layout density, visual hierarchy, control choice, and polished responsive states.
context7
Fast-moving libraries where stale API knowledge causes wrong code.
Install
/plugin install context7@claude-plugins-official Download / source
Why it is best: It pulls current, version-specific documentation into the session. That makes it one of the easiest plugins to justify when framework behavior changed recently.
security-guidance
Teams that want a security pass during implementation, not only at the end.
Install
/plugin install security-guidance@claude-plugins-official Download / source
Why it is best: It adds a security-minded review layer around code changes. It will not replace a human review, but it can catch unsafe defaults, risky patterns, and missing guardrails early.
code-review
Teams that want review agents instead of generic “looks good” responses.
Install
/plugin install code-review@claude-plugins-official Download / source
Why it is best: It gives Claude a more structured review workflow with confidence-filtered findings, which is exactly what you want when you are looking for real defects and regression risk.
pr-review-toolkit
Pull-request-heavy teams that review comments, test failures, types, and quality separately.
Install
/plugin install pr-review-toolkit@claude-plugins-official Download / source
Why it is best: It is narrower than a general review plugin and better when your workflow already revolves around PR checks and review comments.
commit-commands
Developers who repeatedly ask Claude to summarize diffs, write commits, push, and open PRs.
Install
/plugin install commit-commands@claude-plugins-official Download / source
Why it is best: It turns a common end-of-task workflow into repeatable commands. That saves attention and keeps commit messages more consistent.
linear
Teams that use Linear issues as the source of truth for specs and tasks.
Install
/plugin install linear@claude-plugins-official Download / source
Why it is best: The payoff is pulling task context directly into the coding session. Install Linear or Atlassian based on where your team actually works, not because both exist.
figma
Frontend teams that work from Figma files, components, and design tokens.
Install
/plugin install figma@claude-plugins-official Download / source
Why it is best: It gives Claude access to design source material instead of making it infer layout from screenshots or verbal descriptions. Skip it if your design handoff is not actually in Figma.
vercel
Apps deployed on Vercel, Firebase, or Supabase where platform context helps debugging.
Why it is best: Platform plugins are excellent when they match your deploy or backend stack and dead weight when they do not. Pick the one you use every week.
Use firebase or supabase instead if that is your actual stack.
sentry
Production bug triage where stack traces and issue history guide the fix.
Install
/plugin install sentry@claude-plugins-official Download / source
Why it is best: Claude can connect an error report to the relevant code while you are editing. That is a concrete, high-signal use case rather than a vague productivity promise.
slack
Pulling project context out of team conversations when decisions live in Slack.
Install
/plugin install slack@claude-plugins-official Download / source
Why it is best: It can save time when the useful detail is buried in threads. Keep permissions tight, because chat plugins can become noisy and broad very quickly.
skill-creator
People who want to package their own repeatable workflows instead of borrowing someone else's.
Install
/plugin install skill-creator@claude-plugins-official Download / source
Why it is best: It is most useful when you already know the workflow you want and need help turning it into a reusable skill.
superpowers
Developers who want a broad community workflow pack for brainstorming, debugging, TDD, review, and skill authoring.
Install
/plugin install superpowers@claude-plugins-official Download / source
Why it is best: It is process-heavy, so you should read it before installing. But among broad workflow packs, it is one of the few worth evaluating instead of dismissing as a thin wrapper.
If you prefer browsing visually, open claude.com/plugins or run /plugin and use the Discover tab. The install command is the same pattern throughout:
/plugin install github@claude-plugins-official
/reload-pluginsWhy these made the cut
The shortlist above favors plugins with one of three clear payoffs.
They give Claude better signals
LSP plugins, Playwright, Context7, GitHub, Figma, and Sentry all replace guesswork with live information: diagnostics, rendered browser state, current docs, PR context, design files, or stack traces. These are the easiest plugins to justify because they improve the facts Claude works from.
They package a repeatable workflow
code-review, pr-review-toolkit, commit-commands, skill-creator, and superpowers are process plugins. They are worth it when the workflow is something you repeat often enough that a named command or agent saves attention.
They match a platform you already use
Linear, Atlassian, Slack, Vercel, Firebase, Supabase, and Sentry are only “best” if your team already lives there. If not, skip them. A service plugin connected to a tool you barely touch is just extra surface area.
How to judge a plugin before installing
Run any plugin through the same filter:
Keep it or skip it
| What's bundled? | Read the contents. MCP servers mean context cost; hooks mean commands run. |
|---|---|
| Who maintains it? | Official or active project, or an abandoned experiment? |
| Does it fit my stack? | Framework and platform plugins are only useful if they match your work. |
| Could I do it in two minutes? | If it's a thin wrapper around a command you'd write anyway, skip it. |
The “could I do this myself quickly” test filters out a surprising amount. Many plugins wrap a single slash command or one MCP server. If setting that up by hand is trivial — and it often is — you keep more control and avoid trusting someone else’s bundle.
Install lean, review often
Plugins make it easy to accumulate extensions you forgot you have. Periodically list what’s installed and remove what you don’t use, the same way you’d prune dependencies. A bloated plugin set has the same symptoms as too many MCP servers — a tighter context window and slower, vaguer responses. The fix is the same: cut back.
Plugin install checklist
- Read what the plugin bundles before installing
- Check the maintainer and how recently it was updated
- Confirm it matches your actual stack and workflow
- Watch for bundled MCP servers and their context cost
- Prefer building a trivial setup yourself over a thin-wrapper plugin
- Review installed plugins periodically and remove the unused
Wrapping up
Plugins are a real convenience when they bundle a setup you’d otherwise build by hand — a review toolkit, your platform’s integrations, a workflow process. They’re a liability when you install them indiscriminately, because each can bring hooks that run commands and MCP servers that cost context. Judge by what’s inside, who maintains it, and whether it fits your stack, not by the length of any “best plugins” list.
To install plugins and add a marketplace, see the marketplace setup guide. To understand how plugins relate to the pieces they bundle, read plugins vs skills vs MCP.
