Plugins

from athola/claude-night-market

Quality gates for spec-driven development: adversarial plan verification and structured code review.

Reviews and enriches story specifications with codebase-verified sub-tasks, architecture alignment, design simplification, and API test plans.

from kangminhyuk1111/agents

Specification-to-code compliance checker for blockchain audits with evidence-based alignment analysis

from Uniswap/ai-toolkit

from ky1ejs/claude-plugins

from mahidalhan/claude-hacks

from mahidalhan/skilled-intelligence-marketplace

from Pimzino/spec-workflow-mcp

from aaronbassett/aaronbassett-marketplace

from lumberbarons/lumber-mart

from ThilinaTLM/agent-skills

from lifangda/claude-plugins

from Dexploarer/claudius-skills

from timsvoice/specimin

from akiojin/skills

from mattbrailsford/speckl

from thlandgraf/cc-marketplace

from vaayne/agent-kit

from vaayne/cc-plugins

from arittr/spectacular

from wilrf/wilrf-marketplace

Comprehensive SpiceDB development toolkit for designing permission models, generating schemas, implementing authorization, and testing

Spider SSH host management, deployment, and operations skills.

Backend engineer — APIs, system design, performance, distributed systems

Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".

Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".

Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".

Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".