api-builder
Comprehensive API design and development workflow that orchestrates API architecture, endpoint design, documentation generation, and integration patterns. Handles everything from RESTful API creation and GraphQL schema design to API gateway setup and version management.
What this skill does
# API Builder - Complete API Development Workflow ## Overview This skill provides end-to-end API development services by orchestrating API architects, integration specialists, and documentation experts. It transforms API requirements into production-ready APIs with comprehensive design, documentation, testing, and integration capabilities. **Key Capabilities:** - ๐๏ธ **Multi-Protocol API Design** - RESTful APIs, GraphQL, gRPC, and WebSocket implementations - ๐ **Comprehensive Documentation** - Auto-generated API docs, interactive testing, and developer guides - ๐ง **Integration Architecture** - API gateways, middleware, and third-party service integration - ๐ **API Analytics & Monitoring** - Usage tracking, performance monitoring, and error analysis - ๐ก๏ธ **API Security & Governance** - Authentication, rate limiting, and API lifecycle management ## When to Use This Skill **Perfect for:** - RESTful API design and implementation - GraphQL schema development and resolver implementation - API gateway setup and middleware configuration - API documentation generation and developer portal creation - API integration patterns and third-party service connections - API versioning and lifecycle management **Triggers:** - "Design and implement a REST API for [application]" - "Create a GraphQL API with [features]" - "Set up an API gateway with [middleware]" - "Generate comprehensive API documentation" - "Implement API integration with [service]" ## API Development Expert Panel ### **API Architect** (API Design & Architecture) - **Focus**: API design patterns, protocol selection, architectural decisions - **Techniques**: RESTful design, GraphQL schema design, API composition - **Considerations**: Scalability, maintainability, developer experience, performance ### **Integration Specialist** (API Integration & Middleware) - **Focus**: API gateways, middleware, third-party integrations - **Techniques**: API composition, service mesh, event-driven architecture - **Considerations**: Latency, reliability, security, monitoring ### **Documentation Expert** (API Documentation & Developer Experience) - **Focus**: API documentation, developer portals, interactive testing - **Techniques**: OpenAPI/Swagger, GraphQL docs, API testing frameworks - **Considerations**: Developer experience, documentation accuracy, discoverability ### **API Security Specialist** (API Security & Governance) - **Focus**: API security, authentication, authorization, governance - **Techniques**: OAuth 2.0, API keys, rate limiting, threat protection - **Considerations**: Security by design, compliance, usability ### **Performance Engineer** (API Optimization & Monitoring) - **Focus**: API performance, caching, monitoring, analytics - **Techniques**: Response optimization, caching strategies, load balancing - **Considerations**: Response times, throughput, resource utilization ## API Development Workflow ### Phase 1: API Requirements Analysis & Design Planning **Use when**: Starting API development or API modernization **Tools Used:** ```bash /sc:analyze api-requirements API Architect: API design requirements and constraints Integration Specialist: integration points and dependencies Documentation Expert: documentation requirements and developer needs ``` **Activities:** - Analyze business requirements and translate to API specifications - Identify API protocols and architectural patterns - Define API contracts and data models - Plan integration points and external dependencies - Establish API governance and versioning strategy ### Phase 2: API Architecture & Protocol Design **Use when**: Designing the API structure and choosing protocols **Tools Used:** ```bash /sc:design --type api restful-architecture /sc:design --type graphql schema API Architect: comprehensive API design and protocol selection Integration Specialist: integration architecture and patterns ``` **Activities:** - Design API architecture and protocol selection (REST/GraphQL/gRPC) - Create API specifications and data contracts - Design endpoint structures and resource relationships - Plan API composition and orchestration patterns - Define error handling and response formats ### Phase 3: API Implementation & Development **Use when**: Writing the actual API code and business logic **Tools Used:** ```bash /sc:implement api-endpoints API Architect: API implementation patterns and best practices Integration Specialist: middleware and integration implementation API Security Specialist: security controls and authentication ``` **Activities:** - Implement API endpoints and business logic - Create middleware for authentication, validation, and error handling - Implement data validation and serialization - Create API versioning and backward compatibility - Write unit and integration tests for API endpoints ### Phase 4: API Documentation & Developer Experience **Use when**: Creating comprehensive API documentation and developer resources **Tools Used:** ```bash /sc:implement api-documentation Documentation Expert: API docs and developer portal creation API Architect: API specification validation and examples Integration Specialist: integration guides and SDKs ``` **Activities:** - Generate OpenAPI/Swagger specifications - Create interactive API documentation and testing interfaces - Develop SDKs and client libraries - Write integration guides and code examples - Create developer portal and onboarding materials ### Phase 5: API Gateway & Integration Setup **Use when**: Setting up API gateway, middleware, and integrations **Tools Used:** ```bash /sc:implement api-gateway Integration Specialist: API gateway configuration and middleware API Security Specialist: security policies and access control Performance Engineer: caching, rate limiting, and optimization ``` **Activities:** - Configure API gateway with routing and policies - Implement middleware for authentication, rate limiting, and logging - Set up API composition and orchestration - Configure caching and performance optimization - Implement API monitoring and analytics ### Phase 6: API Testing & Quality Assurance **Use when**: Ensuring API reliability, performance, and security **Tools Used:** ```bash /sc:test api-comprehensive Performance Engineer: load testing and performance validation API Security Specialist: security testing and vulnerability assessment Documentation Expert: documentation accuracy and usability testing ``` **Activities:** - Implement comprehensive API test suites (unit, integration, E2E) - Conduct load testing and performance benchmarking - Perform security testing and vulnerability assessment - Validate API contracts and documentation accuracy - Test error scenarios and recovery mechanisms ## Integration Patterns ### **SuperClaude Command Integration** | Command | Use Case | Output | |---------|---------|--------| | `/sc:design --type api` | API design | Complete API architecture | | `/sc:implement restful` | REST API | Production-ready REST endpoints | | `/sc:implement graphql` | GraphQL API | GraphQL schema and resolvers | | `/sc:implement gateway` | API gateway | Configured API gateway | | `/sc:test api` | API testing | Comprehensive test suite | ### **API Protocol Integration** | Protocol | Role | Capabilities | |----------|------|------------| | **RESTful** | Standard API | HTTP-based REST API with proper semantics | | **GraphQL** | Flexible API | Flexible query language and type system | | **gRPC** | High-performance API | Binary protocol for high-performance scenarios | | **WebSocket** | Real-time API | Real-time bidirectional communication | ### **MCP Server Integration** | Server | Expertise | Use Case | |--------|----------|---------| | **Sequential** | API reasoning | Complex API design and problem-solving | | **Web Search** | API patterns | Latest API design trends and best practices | | **Firecrawl** | API testing | External API integration and testing | ## Usage Examples ### Example 1: Complete REST API Development
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.