Api Patterns

This is a decision-making framework for API design, not a collection of boilerplate code. It covers REST versus GraphQL versus tRPC selection, response formats, versioning strategies, authentication patterns, and rate limiting approaches. The skill pushes you to choose based on context rather than defaulting to REST for everything. It includes a content map that tells Claude exactly which file to read for specific questions, from resource naming to OpenAPI documentation. The checklist format is practical: it makes you ask about API consumers and client requirements before jumping into implementation. If you're building APIs and want structured thinking about tradeoffs rather than copy-paste solutions, this handles the architectural decisions upfront.