The Claude Code plugin ecosystem has grown fast. There are now 9,000+ plugins available. Most of them are not useful for PMs. These 10 are. Each one was tested from the view of a product manager who builds prototypes, runs research workflows, and manages backlogs, not a full-time software engineer.
A plugin is a bundle that can include skills (reusable instructions Claude invokes automatically), MCP servers (connectors to external tools like Linear or Figma), hooks (scripts that run on lifecycle events like session start or before a file edit), and subagents (specialized AI workers for specific tasks).
You install plugins via /plugin install [name]@[marketplace] in Claude Code. Official plugins come from Anthropic. Community plugins come from third-party developers via registries like ClaudePluginHub and Claude-Plugins.dev. Most are free and open-source.
| # | Plugin | Verdict summary |
|---|---|---|
| 1 | Superpowers | The best starting plugin collection if you want a proven foundation without researching each plugin individually. |
| 2 | Ralph Wiggum (Ralph Loop)Official | Genuinely powerful for autonomous implementation of well-defined tasks. |
| 3 | Frontend Slides | A PM-specific gem. |
| 4 | gstack | If you want a full, proven setup without building your own from scratch, gstack is the shortcut. |
| 5 | Design Plugin | A solid complement to Frontend Design, especially when you want Claude to think more deliberately about layout and composition before writing any code. |
| 6 | Code Review PluginOfficial | Worth running on any non-trivial PR before engineering review. |
| 7 | Compound Engineering | One of the most thoughtfully designed plugin collections in the ecosystem. |
| 8 | Security Guidance HookOfficial | Install this for every project. |
| 9 | Frontend DesignOfficial | Install it. |
| 10 | AI PM OS | If you are using Claude Code for real PM work, not only prototyping, install this first. |
Curated plugin marketplace with battle-tested engineering workflows
Superpowers is a curated Claude Code plugin marketplace maintained by Jesse Vincent (@obra). It bundles proven workflows for the full development lifecycle: test-driven development, systematic debugging, planning before coding, parallel agent execution, and handoff between sessions. Rather than hunting for individual plugins, you get a vetted collection in one install.
How PMs use it
If you're new to Claude Code and not sure which plugins to start with, Superpowers is the fastest way to get a working setup. The TDD skill forces Claude to write tests before code (dramatically reduces the 'it runs but breaks everything' problem), and the brainstorming skill structures exploratory sessions before jumping into implementation.
Pros
Cons
Install
# Install via skills.sh: npx skills add obra/superpowers # Or install individual skills: /plugin install superpowers@obra
Verdict: The best starting plugin collection if you want a proven foundation without researching each plugin individually. Install it, read the skill list, and activate the ones that fit your workflow.
Docs and GitHubAutonomous multi-hour coding sessions
Ralph Loop turns Claude into a self-driving development agent. It uses a stop-hook pattern that resets context between tasks. That prevents the circular reasoning that derails long sessions. You define a PRD with a list of tasks and run the loop. Claude picks tasks one at a time. It builds the change, commits it to git, resets context, then picks the next one.
How PMs use it
You've got a clear spec for a new feature. Instead of babysitting Claude through 20 back-and-forth exchanges, you write a PRD file listing the specific tasks, start the Ralph Loop, and review the git history two hours later. Works best for well-scoped grunt work: CRUD operations, test coverage, database migrations, form validations.
Pros
Cons
Install
/plugin install ralph-wiggum@anthropic
Verdict: Genuinely powerful for autonomous implementation of well-defined tasks. PMs who write clear PRDs get the most out of it. If your specs are vague, you'll spend more time cleaning up than you would have shipping.
Docs and GitHubBeautiful web presentations from plain English descriptions
Frontend Slides gives Claude the ability to write fully-rendered, animation-rich HTML presentations from a text description. You describe your slides in plain English, or paste in an outline. Claude produces a polished web presentation. You can open it in any browser, share it as a URL, or save it as PDF.
How PMs use it
Sprint reviews, exec updates, and stakeholder demos without touching PowerPoint. Describe your Q3 results in a few bullet points, ask Claude to turn it into a presentation, and get a styled slide deck in under a minute. Can also convert existing PowerPoint files to a web format. Especially useful when you need something quick-but-professional and do not want to spend an hour in Google Slides.
Pros
Cons
Install
# Install via skills.sh: npx skills add zarazhangrui/frontend-slides # Then in Claude: /slides
Verdict: A PM-specific gem. If you're already in Claude Code and need a quick deck, this saves you the context switch to a presentation tool. Not a replacement for major investor decks, but excellent for internal alignment and stakeholder updates.
Docs and GitHubGarry Tan's exact Claude Code setup, 23 specialist commands
gstack is Garry Tan's exact Claude Code setup, open-sourced as a plugin. It installs 23 opinionated slash commands that act as virtual team specialists. CEO covers strategy and scope reviews. Designer covers UI critique. Eng Manager covers architecture lockdown. Release Manager covers shipping. Doc Engineer covers documentation. QA covers systematic testing. Each specialist has a defined role and mode of interaction.
How PMs use it
Instead of figuring out your own Claude Code workflow, gstack gives you a pre-configured team of specialists from day one. Ask the CEO to review your plan before building, the Designer to critique your prototype, and the QA role to find bugs before you share anything. It's the fastest way to get professional-grade structure without learning every Claude Code pattern yourself.
Pros
Cons
Install
# See README for full setup: git clone https://github.com/garrytan/gstack cd gstack && ./install.sh # Or via gstack CLI: npx gstack install
Verdict: If you want a full, proven setup without building your own from scratch, gstack is the shortcut. Treat it as a starting point you can trim to your workflow, not a rigid system you have to follow completely.
Docs and GitHubStructured UI design workflows inside Claude Code
Design Plugin brings structured UI design workflows into Claude Code. It gives Claude a vocabulary and framework for making more intentional design decisions, covering layout composition, visual hierarchy, spacing systems, and component design, rather than writing generic-looking interfaces. Maintained by @0xdesign.
How PMs use it
When your prototype needs to look like something a designer shipped rather than something an AI generated, this plugin shifts Claude's defaults. It's useful when building stakeholder-facing prototypes where visual quality affects how seriously your idea is taken. The plugin also helps Claude be more deliberate about responsive design and accessibility.
Pros
Cons
Install
# Install from GitHub: git clone https://github.com/0xdesign/design-plugin # Follow setup instructions in README
Verdict: A solid complement to Frontend Design, especially when you want Claude to think more deliberately about layout and composition before writing any code. Worth installing if UI quality is a priority for your prototypes.
Docs and GitHubMulti-agent PR analysis before you merge
The Code Review plugin runs five parallel Claude agents against your pull request, each checking a different dimension: CLAUDE.md compliance, bug detection, historical context, PR history, and code comments. Agents score findings by confidence and filter out low-confidence results to reduce noise.
How PMs use it
Before asking your engineering team to review a PR that Claude wrote, run the code review plugin to catch obvious issues. As a PM who's less confident in code quality, this gives you a sanity check layer before escalating to engineers.
Pros
Cons
Install
/plugin install code-review@anthropic # Invoke with: /code-review
Verdict: Worth running on any non-trivial PR before engineering review. Catches the obvious mistakes and helps you communicate more confidently about code quality.
Docs and GitHubFull engineering workflow from brainstorm to shipped PR
Compound Engineering is Every.to's official Claude Code plugin. It is built around the idea that knowledge should compound across sessions. It ships a full set of workflow commands. /ce-brainstorm explores needs before writing code. /ce-plan produces structured implementation plans. /ce-work executes them cleanly. /ce-review runs a structured multi-persona code review. /ce-compound docs what you solved so future sessions benefit from it.
How PMs use it
The brainstorm → plan → work → review loop matches how good PMs think: understand the problem fully before moving to solution. The /ce-compound command is valuable, after solving a tricky problem with Claude, it writes up what was learned as reusable context. You do not repeat the same debugging session a month later.
Pros
Cons
Install
# Install via skills.sh: npx skills add every-marketplace/compound-engineering # Or install the plugin directly: /plugin install compound-engineering@every
Verdict: One of the most thoughtfully designed plugin collections in the ecosystem. The /ce-compound command alone justifies installation, it's the difference between Claude sessions that reset every time and ones that get smarter as you go.
Docs and GitHubPassive safety warnings on every file edit
A PreToolUse hook that monitors nine security anti-patterns, command injection, XSS, dynamic code execution, dangerous HTML rendering, insecure deserialization, and shell execution calls. When Claude edits a file that triggers one of these patterns, you get a warning before the change is applied. Zero setup required.
How PMs use it
If you're building internal tools or prototypes that handle user input, this plugin acts as a passive safety net. You do not need to understand every security vulnerability, the hook will flag. When Claude is writing something potentially dangerous and give you a moment to think before accepting the change.
Pros
Cons
Install
/plugin install security-guidance@anthropic
Verdict: Install this for every project. It costs nothing in tokens or setup, and it catches the security mistakes that are most likely to bite you when moving fast.
Docs and GitHubBetter-looking AI-generated UI
An auto-invoked skill that guides Claude toward production-grade frontend interfaces instead of generic AI aesthetics. When Claude is building UI, the skill activates and provides guidance on typography, spacing, color, visual hierarchy, and interaction design.
How PMs use it
You're building a prototype to show stakeholders. Without this plugin, Claude writes functional but visually generic UIs. With it, you get interfaces that look like something a designer shipped. Better prototypes lead to better feedback and faster stakeholder buy-in.
Pros
Cons
Install
/plugin install frontend-design@anthropic
Verdict: Install it. The quality delta between raw Claude UI and Frontend Design-guided Claude UI is substantial. Essential for PM prototyping.
Docs and GitHub243 PM skills and frameworks built for Claude Code
AI PM OS is a skill collection built for product managers working in Claude Code. It ships 243 PM skills covering discovery, prioritisation, stakeholder communication, roadmapping, and delivery, plus 150+ frameworks and 11 guided workflows. It's the only Claude Code plugin designed from the ground up for PM work rather than engineering work. (Full disclosure: this is prodmgmt.world's own product.)
How PMs use it
Instead of prompting Claude from scratch for every PM task, writing a PRFAQ, running a prioritisation exercise, drafting OKRs, doing a Jobs-to-be-Done interview analysis, the PM OS ships pre-built skills for each. It's the difference between instructing a general assistant and having a specialist who already knows the method.
Pros
Cons
Install
# Included with AI PM OS ($99 one-time): # Access via: https://www.prodmgmt.world/ # After purchase, install skills: npx skills add prodmgmt-world/pm-os
Verdict: If you are using Claude Code for real PM work, not only prototyping, install this first. Nothing else in the ecosystem is purpose-built for product management at this depth.
Docs and GitHubBeyond individual plugins, the ecosystem also has plugin collections, skill marketplaces, and engineering toolkits worth knowing. These are organized by category below.
| Plugin | Use Case |
|---|---|
| Product Management | |
| PM Skills Library → | Reusable skills for strategy, research synthesis, communication, and execution |
| Frontend Slides ↗ | Create beautiful slides on the web using Claude's frontend skills |
| NotebookLM MCP CLI ↗ | MCP server integration for Google NotebookLM - connect your AI workspace to Claude Code |
| Evals Skills ↗ | Skills for AI evals — companion to the "AI Evals For Engineers & PMs" course; covers setting up rigorous quality checks for agent workflows |
| Engineering | |
| Superpowers ↗ | Curated Claude Code plugin marketplace — TDD, debugging, collaboration patterns, and proven engineering techniques |
| Compound Engineering Plugin ↗ | Official plugin for engineering workflow automation — works with Claude Code, Codex, and more. Covers planning, review, and knowledge capture |
| Get Shit Done ↗ | Meta-prompting system that transforms vague ideas into shipped features through spec-driven workflows, multi-agent orchestration, and atomic git commits |
| Vercel Agent Browser ↗ | Browser automation CLI for AI agents |
| Vercel Agent Skills ↗ | Official collection of agent skills from Vercel Labs |
| Shaping Skills ↗ | Claude Code skills for Shape Up methodology - iterate on problems and solutions before implementation with /shaping and /breadboarding workflows |
| gstack ↗ | Garry Tan's exact Claude Code setup — 23 opinionated tools acting as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA |
| Design | |
| Design Plugin ↗ | UI design and prototyping with Claude Code |
| Layers ↗ | Product design skills for making decisions beneath the screen — strategy, user needs, conceptual models, flows, and domain language |
| Emil Kowalski Skill ↗ | Design engineering guidance for better interfaces, animations, performance, and frontend craft inside Claude Code, Cursor, Codex, and other agents |
| User Interface Wiki ↗ | Living manual for better interfaces — curated guidelines for building and reviewing UI with AI agents |
| UI Design Brain ↗ | Best practices, layout patterns, and design-system conventions for 60+ interface components — production-grade UI instead of generic output |
| ui-skills.com ↗ | Opinionated constraints for building better interfaces with agents |
| SuperDesign ↗ | Design discovery and generation - search design prompts, extract brand guidelines, and create design variations on an infinite canvas |
| Impeccable ↗ | Premium frontend design skill with commands for typography, color, motion, polish, audits, browser iteration, and anti-pattern detection |
| Misc | |
| Skills.sh ↗ | Open agent skills ecosystem — one-command installation, compatible with 20+ agent platforms, community-maintained skill leaderboard |
The official Anthropic plugin directory at claude.com/plugins is the authoritative source for official plugins. Community directories like ClaudePluginHub, Claude-Plugins.dev, and the Claude Code subreddit are where you'll find the most active discovery.
A note on community plugins: the ecosystem is moving fast and some published plugins have inaccurate documentation or descriptions. The Claude Code community on Reddit is the best signal for what is working in practice. gstack, Superpowers, and Compound Engineering keep coming up; treat everything else as "try it and see."
For MCP server setup, connecting Claude to external services like Notion, Slack, or your database, see the MCP guide for product managers.
Instead of setting up plugins one by one, AI PM OS gives you a full library of PM-specific skills and workflows. That includes user research synthesis, PRD drafting, competitive analysis, and stakeholder communication. All of it is ready to use with Claude Code.
Most Claude Code plugins from official and community sources are free and open-source. Nine of the ten plugins on this page are free. The exception is AI PM OS ($99 one-time for one PM), a purpose-built skill collection for product managers. The price reflects the depth of PM-specific content rather than platform access.
A plugin is a packaging format that bundles multiple extension types into one installable unit. A skill is a reusable instruction set that Claude invokes automatically or on demand. An MCP server is an external connector that gives Claude access to third-party tools and data. Plugins can contain skills, MCP servers, hooks, and custom agents, all in one install.
Skill descriptions load at session start (low cost). Full content loads only when a skill is invoked. MCP server tool names load at start; full schemas load on demand. Hooks run externally and add zero token cost unless they return context. Plugins with many sub-skills (like gstack or Superpowers) have a slightly higher baseline context load.
Ralph Loop (Ralph Wiggum plugin) enables autonomous coding sessions where Claude implements tasks one at a time, commits to git, resets context, and picks the next task. Use it when you have crystal-clear specs and want to implement without babysitting. Avoid it for exploratory work where requirements are still fuzzy.
Start with three: Security Guidance (always on, zero cost), Frontend Design (if you are prototyping), and either Ralph Loop or Compound Engineering. Pick Ralph Loop for autonomous execution. Pick Compound Engineering for a structured workflow. Add gstack or Superpowers once you have a feel for the basics. More plugins means more context load. Choose quality over quantity.
Yes. A plugin is a directory with a .claude-plugin/plugin.json manifest and optional folders for skills, agents, hooks, and MCP servers. You can start by packaging existing CLAUDE.md skills you have already written. The official docs have a quickstart that walks through building a plugin from scratch.
This page is updated as the Claude Code plugin ecosystem evolves. For the official plugin directory, visit claude.com/plugins. For MCP setup and connecting Claude to external tools, see the MCP guide for PMs.