Claude Code plugins
46 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 46 plugins that match these filters. Clear filters
Parallel Computing Toolbox and MATLAB Parallel Server.
Expert Swift Testing guidance for #expect/#require macros, traits and tags, parameterized tests, async testing patterns, parallel execution, and XCTest migration workflows.
Cross-review code with several console code agents at once: Claude Code, Codex, Coddy, Cursor Agent, Devin, OpenCode and others review the same brief in parallel and blind to each other, then the orchestrating agent verifies every finding against the code and decides alone what matters and what to fix. Linux, macOS and Windows; reviewers chosen once per agent, for one project or for all of them.
workflow
Use before any Pruna or Replicate HTTP call — credentials, upload/poll/download, parallel batches, and agent safety.
Use for Six Thinking Hats or de Bono's parallel thinking, or when a decision or idea needs facts, gut feel, risks, benefits and new options kept apart: "look at this from all sides", "full perspective check". Skip for plain factual questions or single-angle hot takes.
Explores a codebase for architectural friction through the lens of Ousterhout's deep-module principle (small interface, large implementation). Seven-step interactive workflow: an Explore sub-agent navigates the codebase organically — the friction it experiences IS the signal. Surfaces candidate clusters with coupling reasons, call patterns, shared types, dependency categories, and existing tests that a boundary test would replace. User picks what to explore, frames the problem, then 3–4 parallel sub-agents design competing deep-module interfaces. Chosen design becomes a structured RFC action file readable by GitHub MCP or ROVO (Jira) MCP. Use when the user says "arch review", "find shallow modules", "module depth", "deep module", "Ousterhout", "testability audit", "surface coupling", "design interfaces", "RFC issues", or "architectural friction".
