What problem does it solve?
API design and governance across teams is often inconsistent, leading to fragile integrations and security gaps. This skill provides a domain-first approach to choosing REST vs GraphQL, enforcing contract-first design, and standardizing security, validation, and versioning practices.
Core Features & Use Cases
- Consistent API strategy: guidance on when to use REST vs GraphQL or tRPC based on complexity and client needs.
- Production-grade patterns: contract-first OpenAPI/SDL, standard envelopes for responses, inclusive error handling, authentication, rate limiting, and versioning.
- Real-world scenarios: building a multi-client API for web and mobile with secure authentication and smooth migration paths.
Quick Start
Ask me to evaluate REST or GraphQL for your project and implement a production-ready API following the recommended patterns.