Claude Code plugins
5 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 5 plugins that match these filters. Clear filters
14 bundled product skills with 19 Python tools: product-skills fork-orchestrator with continuous-discovery loop (deterministic 16-lane router, Torres cadence tracker, OST linter, /cs-product + /cs-grill-product + /cs-product-loop), product manager toolkit (RICE, PRDs), product strategist, UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, product analytics, experiment designer, product discovery, roadmap communicator, spec-to-repo, design-qa (UI finish gate: inert controls, missing states, rendered WCAG 2.2 checks). Companion standalone plugins: agile-product-owner, code-to-prd, apple-hig-expert, research-summarizer, design-qa.
Your AI development teammate. Turns a story file into a shipped, reviewed, and tested feature via orchestrator → architect → developer → PR reviewer → QA → Playwright.
Autonomous multi-agent development framework with spec-driven sprints. Write specs, run /sprint, and let coordinated agents (backend, frontend, QA, UI testing) handle implementation through self-iterating convergent loops.
Gate a UI before it is called done: check the build, not the design file. Three deterministic stdlib scripts: a finish linter that blocks on controls that do nothing, dead links, placeholder copy and removed focus rings, and warns on template defaults; an interaction-state checker that derives loading, empty, error, busy and focus states from each surface's kind and blocks when they are missing or unevidenced; and a rendered audit that reads a browser snapshot and blocks on WCAG 2.2 AA failures in contrast, focus visibility, focus obscured, reflow at 320 px, accessible names and target size. Ships a read-only snapshot collector, an optional Playwright keyboard pass, cs-design-qa agent, /cs-design-qa and /cs-ui-finish-lint commands, 3 cited references and a finish sign-off.
Turn a spec or a Jira issue into test cases in your team's format. Approve one plan, get one Excel or CSV file your TMS imports, the gaps found in the spec, and a Postman collection for APIs.