The 14 Claude Code plugins that help product managers in 2026 are 3 for PM work (AI PM OS, Evals Skills, NotebookLM MCP CLI), 8 for design (Design and Refine, Taste Skill, Hallmark, UI UX Pro Max, Layers, MengTo Skills, Refactoring UI Skills, Emil Kowalski's Skills), and 3 for engineering (Matt Pocock's Skills, Addy Osmani's Agent Skills, Ponytail). 13 of them are free. Start with Taste Skill if you prototype, run /grill-me before you build, and run /ponytail-review before you hand a branch to engineers.
The Claude Code plugin ecosystem has grown fast. There are now 9,000+ plugins available. Most of them are not useful for PMs. These 14 are, grouped by the job they do: PM craft, design, and engineering. Each one was picked from the view of a product manager who builds prototypes, runs research workflows, and manages backlogs, not a full-time software engineer. Install after Claude Code setup, not instead of it.
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 | |
|---|---|---|---|
| PM plugins | |||
| 1 | AI PM OS | If you are using Claude Code for real PM work, not only prototyping, install this first. | |
| 2 | Evals Skills | The best PM-facing skill pack for AI features. | |
| 3 | NotebookLM MCP CLI | The fastest way to turn a pile of research into cited answers. | |
| Design plugins | |||
| 4 | Design and Refine | The best way to explore a UI direction before committing. | |
| 5 | Taste Skill | Install it before your next prototype. | |
| 6 | Hallmark | The best pick when the page itself is the product: a launch page, a pitch prototype, or anything stakeholders judge in five seconds. | |
| 7 | UI UX Pro Max | Use it at the start of a new prototype to pick a design direction that fits the product, then let Taste Skill or Hallmark handle the polish. | |
| 8 | Layers | The most PM-friendly design plugin here. | |
| 9 | MengTo Skills | Cherry-pick, do not install everything. | |
| 10 | Refactoring UI Skills | The finishing pass. | |
| 11 | Emil Kowalski's Skills | The polish layer for motion. | |
| Engineering plugins | |||
| 12 | Matt Pocock's Skills | Install it and make /grill-me a habit before every non-trivial request. | |
| 13 | Addy Osmani's Agent Skills | The most complete engineering workflow on this list. | |
| 14 | Ponytail | An easy always-on install. | |
Built for product management work rather than code: the PM craft itself, judging AI features, and research synthesis.
231 PM skills, 150+ frameworks, and 11 guided workflows for PM work
AI PM OS is a skill collection built for product managers working in Claude Code. It ships 231 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, AI 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.
See AI PM OSProduct-specific AI evals from the AI Evals course
Evals Skills come from Hamel Husain and Shreya Shankar, who teach the AI Evals course and have helped 50+ companies with evals. An evals-start skill looks at your situation and routes you. eval-audit inspects an existing eval pipeline and ranks its problems by severity. error-discovery builds a review app for your traces, picks a diverse sample, and sorts your notes into failure modes. Other skills generate synthetic test data, write code checks and LLM judges, and calibrate those judges against human labels.
How PMs use it
If you own an AI feature, "it seems fine" is not a quality bar. Point error-discovery at a file of real outputs and you read and annotate them in a simple review app while the agent groups your notes into failure modes. That gives you a ranked list of what is actually going wrong before anyone writes an eval, which is the step most teams skip.
Pros
Cons
Install
npx skills add https://github.com/ai-evals-course/evals-skills # Then point the agent at your data: # "Can you help me do error analysis on traces.jsonl?"
Verdict: The best PM-facing skill pack for AI features. Install it the week your team ships anything built on an LLM.
Docs and GitHubDrive NotebookLM from Claude: sources, questions, and audio overviews
NotebookLM MCP CLI (by Jacob BD) connects Claude and other agents to Google's NotebookLM, which Google now calls Gemini Notebook. It ships an nlm command line tool and an MCP server with 53 tools. Your agent can create notebooks, add URLs, Drive files, and documents as sources, ask questions across them, and generate audio overviews, videos, and slide decks. A setup wizard finds the AI tools on your machine and connects them.
How PMs use it
Research synthesis is where NotebookLM shines, but loading sources by hand is slow. Ask Claude to create a notebook from your interview notes, competitor pages, and support tickets, then query it for patterns with citations back to the source. Generate an audio overview for stakeholders who will not read the doc.
Pros
Cons
Install
uv tool install notebooklm-mcp-cli nlm login # Connect Claude Code and your other AI tools: nlm setup
Verdict: The fastest way to turn a pile of research into cited answers. Use it for personal research, not for anything that has to be reliable.
Docs and GitHubClaude writes working UI by default, not good-looking UI. These eight raise the floor: one explores variations, two set taste, one picks a design system, one fixes thinking beneath the screen, and three add polish.
Five real UI variations side by side, then refine until you are sure
Design and Refine (by @0xdesign) generates five distinct variations of any component or page in your actual codebase. It reads your Tailwind config, CSS variables, or component library first, so variations match your design system. You compare them side by side in a design lab route on your dev server, leave Figma-style comments on any element, and it synthesizes a refined version. When you are done it deletes the temp files and writes a DESIGN_PLAN.md.
How PMs use it
Stakeholder alignment on UI is slow when everyone is reacting to descriptions. Run /design-and-refine:start in Claude Code (or /design-lab in Cursor) on the screen you are debating, and you get five real options exploring different layouts, densities, and interaction patterns. Show those instead of arguing about adjectives. The feedback overlay means you can point at the exact button you mean.
Pros
Cons
Install
# Claude Code: /plugin marketplace add 0xdesign/design-plugin /plugin install design-and-refine@design-plugins /design-and-refine:start # Cursor or Codex: npx skills add https://github.com/0xdesign/design-plugin --skill design-lab # Then in Cursor: /design-lab
Verdict: The best way to explore a UI direction before committing. Use it when you are stuck between options or need stakeholders to react to something concrete.
Docs and GitHubAnti-slop rules that stop AI UI from looking generic
Taste Skill is a set of portable agent skills that push AI-built interfaces toward stronger layout, typography, motion, and spacing. The default skill reads your brief, infers a design language, and tunes three dials: variance, motion, and density. Variants cover redesigning an existing project, calm premium UI, minimalist editorial UI, and brutalist layouts, plus image-generation skills for reference boards.
How PMs use it
Your prototype is the first thing stakeholders judge, and generic AI styling makes a good idea look half-baked. Install the default skill and Claude stops reaching for the same centered hero and purple gradient. If you already have a product, the redesign skill audits the existing UI first, then fixes layout, spacing, and hierarchy.
Pros
Cons
Install
# Default skill: npx skills add https://github.com/Leonxlnx/taste-skill --skill design-taste-frontend # Or install every skill in the pack: npx skills add https://github.com/Leonxlnx/taste-skill
Verdict: Install it before your next prototype. It is the fastest fix for AI UI that looks like AI UI.
Docs and GitHubA design skill that refuses to look AI-generated
Hallmark (from Together AI) picks a page structure for your brief, dresses it in one of twenty-one themes, and runs 57 slop-test gates plus a self-critique before it hands anything back. It has four verbs: build new UI, audit existing code against its anti-patterns, redesign a page while keeping the copy and information architecture, and study a screenshot or URL you admire to extract its structure, type pairing, and colour anchor.
How PMs use it
Two pages built for two different briefs should not look like colour swaps of the same template. Run hallmark audit on your current prototype for a punch list of what makes it look AI-built, with no edits. When a competitor's page has the feel you want, hallmark study pulls out the design DNA without copying it pixel for pixel.
Pros
Cons
Install
npx skills add nutlope/hallmark # Then in Claude: hallmark audit <file or folder> hallmark study <screenshot or URL>
Verdict: The best pick when the page itself is the product: a launch page, a pitch prototype, or anything stakeholders judge in five seconds.
Docs and GitHubA searchable design system brain for your agent
UI UX Pro Max gives your agent a searchable library of design knowledge: 50 active UI styles, 192 colour palettes matched to product types, 74 font pairings, 25 chart types, and 119 UX guidelines covering accessibility and common production failures. Its design system generator reads your project and recommends a page pattern, style, palette, and type pairing with the reasoning behind each choice. It covers 22 stacks, from React and Tailwind to SwiftUI and Flutter.
How PMs use it
When you start a prototype with no design system, Claude guesses. Describe your product and audience, and UI UX Pro Max proposes a full design system that fits the category, for example calm and trust-heavy for a health app, dense and data-first for a dashboard. The chart recommendations help when your prototype is a metrics view.
Pros
Cons
Install
/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill /plugin install ui-ux-pro-max@ui-ux-pro-max-skill
Verdict: Use it at the start of a new prototype to pick a design direction that fits the product, then let Taste Skill or Hallmark handle the polish.
Docs and GitHubProduct design decisions beneath the screen
Layers (by Jamie Mill) is a product design framework packaged as skills. It splits design into seven layers, from observed behaviour and domain language up through user needs, product strategy, conceptual model, interaction flow, and finally surface. Each /layers-* skill works one layer, and an orient skill tells you which layer your problem actually lives in.
How PMs use it
Most bad screens are bad decisions made one layer down. Before you prototype, run the orient skill on your feature and let it tell you whether the gap is in user needs, the conceptual model, or the flow. It is the closest thing to having a senior product designer ask you the uncomfortable questions first.
Pros
Cons
Install
npx skills add jamiemill/layers-skills # Then run any /layers-* skill, starting with: /layers-orient
Verdict: The most PM-friendly design plugin here. Use it before Taste Skill or Design and Refine, not instead of them.
Docs and GitHub150+ design and build skills from the founder of Design+Code
Meng To's skills library holds 150+ portable SKILL.md playbooks for designers and builders. The flagship workflow turns a screen recording of a design into a detailed recreation prompt, turns existing HTML into reusable interaction prompts, and captures full-page references. The web design set covers landing pages, pricing pages, scroll motion, WebGL effects, layout systems, and dozens of visual styles.
How PMs use it
When you know the feel you want but cannot describe it, record a competitor's page or a site you admire and run the video-to-superprompt skill. You get a detailed prompt Claude can build from. The landing-page and pricing-page skills are a fast start for launch pages and pricing experiments.
Pros
Cons
Install
# Clone, then copy the skills you want into ~/.claude/skills/ git clone https://github.com/MengTo/Skills ~/.local/share/mengto-skills cp -r ~/.local/share/mengto-skills/agent-skills/codex/video-to-superprompt ~/.claude/skills/
Verdict: Cherry-pick, do not install everything. Grab the reference-capture workflow and the landing-page skills and ignore the rest until you need them.
Docs and GitHubTen structured design-review skills for extra polish
Refactoring UI Skills packages the principles from Adam Wathan and Steve Schoger's book Refactoring UI as ten focused skills: visual hierarchy, typography scale, color palette, spacing, button hierarchy, visual clutter, empty states, shadows, contrast, and grouping. A refactor-ui meta-skill runs a full design pass. Works in Claude Code, Codex, and Cursor. (Full disclosure: I built this one. It is not affiliated with Tailwind Labs, and the book is worth buying.)
How PMs use it
Your prototype works and looks fine, but something feels off. Run /refactor-ui on the screen for a full review, or call one skill, like the button hierarchy or empty states skill, when you know where the problem is. Each skill explains the principle behind the fix, so you learn to spot the issue yourself next time.
Pros
Cons
Install
/plugin marketplace add gnurio/refactoring-ui-plugin /plugin install refactoring-ui-skills@refactoring-ui-plugin # Then in Claude: /refactor-ui
Verdict: The finishing pass. Use Taste Skill or Design and Refine to get a direction, then run this before you show anyone.
Docs and GitHubAnimation and interface craft from a design engineer at Vercel and Linear
Emil Kowalski built animation and interface work at Vercel and Linear, and made the Sonner toast library. His skills list the small mistakes agents make and how to fix them, like an ease-in curve on an enter animation or a solid border where a soft shadow belongs. The main emil-design-eng skill covers animation and design, and focused skills build animations, review or improve existing ones, find places that deserve motion, make a web app feel native on a phone, and pick a trusted UI library instead of hand-rolling one.
How PMs use it
Motion is where AI prototypes give themselves away: everything slides in the same way, or nothing moves at all. Run improve-animations on your prototype for a prioritised list of fixes any agent can carry out. Use animation-vocabulary to learn the words that get the animation you picture, so your feedback to Claude, or to a designer, gets specific.
Pros
Cons
Install
npx skills@latest add emilkowalski/skills
Verdict: The polish layer for motion. Add it once your prototype looks right and you want it to feel right too.
Docs and GitHubThese keep Claude aligned with what you meant, stop it from over-building, and catch mistakes before an engineer has to.
Small, composable skills for real engineering, not vibe coding
Matt Pocock (Total TypeScript, AI Hero) open-sourced the skills he uses daily. They are deliberately small and composable instead of owning your whole process. The most popular are /grill-me, which makes the agent interview you in detail before any work starts, and /grill-with-docs, which does the same while building a shared vocabulary for your domain. A setup skill connects them to your issue tracker (GitHub, Linear, or local files).
How PMs use it
The most common failure with AI agents is that they build something you did not mean. Run /grill-me before any feature, spec, or even a strategy doc, and Claude asks the questions a good engineer would ask in refinement. It works for non-code work too, which makes it the most useful engineering skill for PMs.
Pros
Cons
Install
/plugin install mattpocock-skills # Then, once per repo: /setup-matt-pocock-skills # Other agents: npx skills@latest add mattpocock/skills
Verdict: Install it and make /grill-me a habit before every non-trivial request. It fixes misalignment at the cheapest possible moment.
Docs and GitHubA senior engineerβs workflow from spec to ship
Addy Osmani, an engineering leader at Google, packaged the workflows and quality gates senior engineers use into 25 skills. Nine slash commands map to the development lifecycle: /spec, /plan, /build, /test, /constraints, /review, /webperf, /code-simplify, and /ship. Skills also trigger on their own, so building UI pulls in frontend guidance and designing an API pulls in interface design. An interview-me skill questions you about requirements one question at a time.
How PMs use it
PMs already think in specs. Run /spec on a feature idea and Claude writes the spec before any code, then /plan breaks it into small tasks you can read and challenge. That gives you a checkpoint where your product judgement matters most, before the agent commits to an approach. /ship walks through the checks you would expect before anything goes live.
Pros
Cons
Install
/plugin marketplace add addyosmani/agent-skills /plugin install agent-skills@addy-agent-skills # Other agents: npx skills add addyosmani/agent-skills
Verdict: The most complete engineering workflow on this list. Install it when your prototypes start turning into real features someone will maintain.
Docs and GitHubMakes your agent think like the laziest senior dev in the room
Ponytail puts a minimalist senior engineer inside your agent. Before writing code it checks whether the browser, the platform, or an installed dependency already solves the problem. Ask for a date picker and you get a native date input instead of a new library and a wrapper component. The author's benchmark on real Claude Code sessions measured about 54% less code and 20% lower cost on average, with safety checks kept. It also ships review, audit, and tech-debt skills.
How PMs use it
Prototypes rot when the agent adds a library for every small feature. With Ponytail on, your prototypes stay small enough to understand, cheaper to run, and easier to hand to an engineer. Run /ponytail-review on a branch Claude built to find what could be deleted.
Pros
Cons
Install
# Send these as two separate prompts: /plugin marketplace add DietrichGebert/ponytail /plugin install ponytail@ponytail
Verdict: An easy always-on install. It quietly removes the most common source of bloated AI-built prototypes.
Docs and GitHubThe official Anthropic plugin directory at claude.com/marketplace/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. Check a repo's recent activity and README before you install, and treat anything new 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. 13 of the 14 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. Large skill packs (like MengTo Skills or the full Taste Skill pack) have a slightly higher baseline context load, so install only the skills you use.
Start with Taste Skill. It gives the biggest jump in visual quality for the least setup. Try Hallmark instead if you mostly build landing pages, and use UI UX Pro Max to pick a design system when a prototype starts from nothing. Add Layers when the problem is the product decision rather than the pixels, Design and Refine when you need options to compare, Refactoring UI Skills for a final polish pass before you show stakeholders, and Emil Kowalski's skills when the motion feels off.
Start with three: Taste Skill (if you prototype), Matt Pocock's skills for /grill-me, and Ponytail to keep the code small. Add Addy Osmani's skills when prototypes turn into real features, and the other design plugins when you need them. 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/marketplace/plugins. For MCP setup and connecting Claude to external tools, see the MCP guide for PMs.