backend-design
Designs comprehensive backend systems including RESTful APIs, microservices, database architecture, authentication/authorization, caching strategies, message queues, and scalability patterns. Produces API specifications, database schemas, architecture diagrams, and implementation guides. Use when designing backend services, APIs, data models, distributed systems, authentication flows, or when users mention backend architecture, API design, database design, microservices, or server-side development.
What this skill does
# Backend Design ## Workflow Follow this systematic design process: 1. **Requirements Analysis** - Gather functional requirements (features, operations) - Define non-functional requirements (performance, scalability, availability) - Identify constraints (budget, timeline, technology, compliance) 2. **Architecture Selection** - Choose architecture pattern (monolith, microservices, serverless) - Select technology stack based on requirements - Define service boundaries and responsibilities 3. **API Design** - Design RESTful endpoints with proper resource modeling - Define request/response schemas and contracts - Plan versioning strategy and documentation - See [api-design-guide.md](references/api-design-guide.md) for REST/GraphQL/gRPC patterns 4. **Database Design** - Model entities and relationships - Design schema with normalization - Plan indexing and partitioning strategies - See [database-design.md](references/database-design.md) for relational and NoSQL patterns 5. **Security Design** - Design authentication flow (OAuth 2.0, JWT) - Plan authorization model (RBAC, ABAC) - Define data encryption and protection strategy 6. **Scalability & Performance** - Design caching strategy (Redis, CDN) - Plan load balancing and auto-scaling - Define asynchronous processing with message queues 7. **Documentation** - Create API specifications (OpenAPI/Swagger) - Document architecture decisions with Mermaid diagrams - Provide implementation guidelines and roadmap ## Output Structure Present your backend design with these sections: 1. **System Overview** - High-level architecture, components, technology stack 2. **API Specification** - Endpoints, schemas, authentication, OpenAPI docs 3. **Database Design** - ERD, schema, indexes, migration plan 4. **Architecture Decisions** - Service decomposition, communication patterns, consistency model 5. **Security Implementation** - Authentication/authorization flows, encryption 6. **Scalability Plan** - Load balancing, caching, database scaling, auto-scaling 7. **Deployment Architecture** - Containers, infrastructure, CI/CD, monitoring 8. **Implementation Roadmap** - Phases, milestones, dependencies, risks ## Core Principles - **API-first approach** - Design and document APIs before implementation - **Security by design** - Build authentication, authorization, and encryption from the start - **Design for scalability** - Plan for growth with caching, load balancing, and horizontal scaling - **Plan for failure** - Include error handling, retries, circuit breakers, and graceful degradation - **Document thoroughly** - Create clear API specs, Mermaid architecture diagrams, and implementation guides ## Reference Files Load additional resources based on specific needs: - **Detailed Design Process**: See [backend-design-process.md](references/backend-design-process.md) for comprehensive step-by-step workflow with examples for API design, database modeling, authentication flows, and microservices patterns - **API Design Guide**: See [api-design-guide.md](references/api-design-guide.md) when designing RESTful APIs, GraphQL schemas, or gRPC services - includes resource modeling, status codes, versioning strategies, and documentation - **Database Design**: See [database-design.md](references/database-design.md) for detailed guidance on relational and NoSQL database design, normalization, indexing, partitioning, and replication strategies - **Best Practices**: See [best-practices.md](references/best-practices.md) for API design, database optimization, security hardening, performance tuning, and reliability patterns - **Common Patterns**: See [common-patterns.md](references/common-patterns.md) for code examples of repository pattern, service layer, dependency injection, and other architectural patterns - **Example Projects**: See [examples.md](references/examples.md) for complete architecture examples including e-commerce systems, real-time chat applications, and microservices implementations
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.