Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
Reviews changed or existing project infrastructure, CI/CD, deployments, release artifacts, recovery, retention, and monitoring for demonstrated failures and worthwhile alternatives. Reviews only; does not edit or decide whether the result ships.
Reviews user-spec interview evidence against project knowledge and code research to diagnose unresolved requirements before drafting. Use when: interview cycles are complete and completeness must be checked before drafting. Diagnoses gaps only; follow-up questions, requirement choices, and drafting decisions are out…
Reviews visual fidelity and responsive layout after layout-writing work. Uses supplied source and captured evidence, and may challenge the visual approach within that lane. Does not modify code or decide whether the result ships.
Verifies factual user-spec claims against the current codebase, including paths, symbols, dependencies, integrations, behavior, and project patterns. Use when: validating the factual-codebase lane; solution adequacy and document quality are out of scope.
Reviews a skill's form against skill-master: frontmatter, routing, package structure, references, line limits, instruction style, and applicable skill-type conventions.
Reviews written test code before or after implementation and diagnoses demonstrated gaps in scenario coverage, assertions, boundaries, and test quality.
Reviews user-spec feasibility, proportionality, architecture compatibility, over- or under-engineering, and concrete simpler alternatives against the current project. Use when: the user-spec is ready for pre-approval solution review; document quality and factual codebase claims are out of scope.
Reviews user-spec document quality: structure, interview coverage, behavioral clarity, verification, edge-case presence, contradictions, and template compliance. Use when: the user-spec is ready for pre-approval document review; solution adequacy and factual codebase claims are out of scope.
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: