What problem does it solve? Teams building APIs often end up with inconsistent URL structures, ad-hoc error formats, missing pagination, and unclear versioning rules, which makes APIs hard to consume and maintain. ## Core Features & Use Cases - Paradigm Selection Guidance: Compares REST, tRPC, and GraphQL with concrete trade-offs so you pick the right approach for public APIs, internal TypeScript monorepos, or complex client queries. - Standardized Conventions: Provides URL structure, HTTP status codes, success/error response envelopes, cursor and offset pagination, filtering/sorting syntax, and deprecation policy. - Implementation Patterns: Includes tRPC router/middleware examples, OpenAPI schema generation, webhook delivery with HMAC signature verification, and per-endpoint rate limiting. - Use Case: When designing a new projects API, load this skill to get a complete checklist covering validation, idempotency keys, caching headers, and audit logs before writing any endpoint code. ## Quick Start Ask the agent to design a versioned REST API for a projects resource with cursor pagination, standardized error responses, and webhook support.
