A curated collection of Claude Code plugins for enhanced development workflows.
Agent
Part of guild
Use this agent when the guild needs architectural planning. The architect reads requirements, analyzes the codebase, and produces implementation plans with specific developer tasks. Spawned directly by the new-requirement skill, alongside the product-owner — not spawned via a board ticket.
Agent
Part of guild
Use this agent when the guild needs code implementation in a Svelte or SvelteKit web application. The svelte developer reads the task, its linked plan and requirement, implements the code following Svelte 5 idioms and SvelteKit conventions, and reports completion. Spawned by the check-in skill when an implementation…
Agent
Part of guild
Use this agent when the guild needs code implementation. The developer reads the task, its linked plan and requirement, implements the code, and reports completion. Spawned by the check-in skill when an implementation task is on the board.
Agent
Part of guild
Use this agent when the guild needs to gather, refine, or document requirements. The product-owner interviews the user, creates requirement documents, and collaborates with the architect. Spawned directly by the new-requirement skill for a live interview with the user (via relay) and, when in scope, the architect …
Agent
Part of guild
Use this agent when you need to verify that recent code changes satisfy all requirements from a plan document. Examples: Context: User has completed implementing features from a phase plan user: "Review if my recent changes satisfy all the requirements in the phase 3 plan" assistant: "I'll use the Task tool to launch…
Agent
Part of guild
Use this agent when the guild needs a QA strategy: deciding what quality means for a product, mapping risk, and planning what to test. The strategist surveys the running product and its specs, builds a coverage matrix and an adversarial what-if input matrix, then declares qa-tester missions. It is the planning half of…
Agent
Part of guild
Use this agent when the guild needs to empirically test a running product: drive real scenarios, observe actual behavior, author end-to-end (Playwright) regression specs, and file reproducible bugs. The execution half of the guild's independent QA discipline. Authors e2e specs (devs co-maintain); covers e2e against…
Agent
Part of guild
Use this agent when the guild needs documentation research, API investigation, or technology evaluation. The researcher gathers information and writes findings into a reference document. Most often spawned directly and inline by the product-owner or architect for a quick lookup; can also be dispatched by check-in…
Agent
Part of guild
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.
Agent
Part of guild
Use this agent for business logic code review. Verifies that acceptance criteria are met, business rules are correctly implemented, and the code is testable with proper unit test coverage. Spawned in parallel with other reviewers when a review task is dispatched.
Agent
Part of guild
Use this agent for edge case code review. Identifies unhandled boundary conditions, null/empty inputs, error scenarios, concurrency issues, and other robustness gaps. Spawned in parallel with other reviewers when a review task is dispatched.
Agent
Part of guild
Use this agent for security-focused code review. Evaluates implementation against OWASP Top 10, checks for injection risks, authentication/authorization flaws, and sensitive data handling issues. Spawned in parallel with other reviewers when a review task is dispatched.
Agent
Part of guild
Use this agent when the guild needs a test plan after development completes. The test-planner inventories what was implemented, maps acceptance criteria to unit and integration test cases, writes the test plan as a plan slice, and declares the test-writer tickets that implement it. Spawned by the check-in skill when a…
Agent
Part of guild
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
Agent
Part of research
The peer-reviewed-evidence lens for STORM research. Use when you need what the actual studies and data show — including conflicting findings, effect sizes, and the quality of the evidence base. Spawned in parallel by the storm-research and multi-perspective-scan skills, one of five expert personas. Writes its analysis…
Agent
Part of research
STORM Phase 2 analyst. Reads multiple perspective analyses (or any set of sources/viewpoints) and maps where they disagree, where they agree, and what none of them addressed. Surfaces the contradictions where real understanding lives. Spawned by the storm-research and contradiction-map skills. Writes…
Agent
Part of research
The incentives-and-money lens for STORM research. Use when you need to follow the money: who profits, who pays, what incentives are misaligned, what the market structure rewards. Spawned in parallel by the storm-research and multi-perspective-scan skills, one of five expert personas. Writes its analysis to the run…
Agent
Part of research
The long-memory, pattern-and-precedent lens for STORM research. Use when you need historical parallels, prior cycles, and "we have seen this before" context that the present-focused perspectives miss. Spawned in parallel by the storm-research and multi-perspective-scan skills, one of five expert personas. Writes its…
Agent
Part of research
STORM Phase 4 auditor. Performs a rigorous, adversarial self-review of a research briefing and its supporting perspectives — fact-checking and hallucination audit, bias detection, completeness check, fairness of contradiction handling, and actionability. Closes STORM's known no-self-critique weakness. Spawned by the…
Agent
Part of research
The hands-on operator's lens for STORM research. Use when you need the view of someone who works with a topic every day — what actually works in practice vs. theory, the failure modes nobody documents, the tacit knowledge. Spawned in parallel by the storm-research and multi-perspective-scan skills, one of five expert…
Agent
Part of research
The adversarial critic's lens for STORM research. Use when you need someone highly critical of the mainstream view to surface flaws, overclaims, hidden problems, and failure cases. Spawned in parallel by the storm-research and multi-perspective-scan skills, one of five expert personas. Writes its analysis to the run…
Agent
Part of research
STORM Phase 3 analyst. Reads the multi-perspective analyses and the contradiction map, then produces a single coherent, cited research briefing that no individual perspective could write: synthesized narrative, explicit handling of contradictions, reliability ranking, open questions, and concrete recommendations.…
Agent
Part of storytelling
Audits a draft against the storytelling framework it's aiming for and the audience it's meant for, then returns a tightened version plus specific fixes. Scores framework-fit, clarity, and impact. Spawned by the storytelling skill to sharpen a chosen draft for high-stakes messages (keynote, investor pitch, launch) or…
Agent
Part of storytelling
Drafts a message in ONE specified storytelling framework (Golden Circle, Pyramid Principle, Pixar Pitch, StoryBrand, What/So What/Now What, or ABT). Given raw material, an audience, a desired outcome, and a medium, it returns a finished, natural-sounding draft in that framework's shape. Spawned in parallel by the…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: