api-patterns

Choosing between REST, GraphQL, and tRPC for API design depends on your system requirements, such as whether you need stateless scalability, flexible querying, or TypeScript monorepo efficiency. The Skill provides decision-making guidance to select the right API style for different scenarios.

Best practices for API versioning and pagination in modern web applications involve standardizing response formats and controlling data payload sizes. This Skill covers these implementation details to ensure your API remains scalable and efficient as your application grows.

To design an API for a real-time application requiring low latency and high scalability, you must apply targeted API design principles and style selection. This Skill analyzes REST, GraphQL, and tRPC to determine the best approach for modern web applications.

tRPC for API development is specifically designed for TypeScript monorepos to provide end-to-end type safety. Using it outside of a TypeScript environment is not its intended use case, and the Skill focuses on its application within that specific architectural context.

You should not use GraphQL over REST for API development when your system requires simple resource-based interactions without complex querying needs, as REST principles offer a more straightforward implementation. The Skill provides comparative analysis to help identify these constraints.