api-patterns

Structured decision-making framework for selecting and designing APIs across REST, GraphQL, and tRPC patterns. API design principles and decision-making for 2025. Learn to THINK, not copy fixed patterns. Read ONLY files relevant to the request! Check the content map, find what you need. Before designing an API: DON'T: DO: This skill is applicable to execute the workflow or actions described in the overview. - Provides a content map covering API style selection, resource design, response formats, versioning strategies, authentication, rate limiting, and security testing - Includes decision trees and checklists to guide API type selection based on consumer requirements and project context - Documents anti-patterns (verb-based endpoints, inconsistent responses, exposed errors) alongside recommended practices for each API style - Covers authentication options (JWT, OAuth, Passkeys, API Keys), pagination approaches, and OpenAPI documentation standards - Default to REST for everything - Use verbs in REST endpoints (/getUsers) - Return inconsistent response formats - Expose internal errors to clients - Skip rate limiting - Choose API style based on context - Ask about client requirements - Document thoroughly - Use appropriate status codes - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific...