What problem does it solve? Designing consistent REST APIs is hard: teams often return 200 for every response, mix verbs into URLs, skip pagination, and invent ad-hoc error formats. This Skill supplies a complete set of conventions and implementation patterns so endpoints are predictable, secure, and developer-friendly. ## Core Features & Use Cases - Resource and URL Conventions: Enforces plural, kebab-case, noun-based URLs with correct HTTP method semantics and status codes (201 with Location, 422 for validation, 429 for rate limits). - Pagination, Filtering, and Sorting: Provides offset and cursor pagination patterns with guidance on when to use each, plus query parameter conventions for filtering, sorting, search, and sparse fieldsets. - Standard Response Formats: Defines success, collection, and error response envelopes with field-level validation details, plus rate limiting headers and versioning strategy. - Implementation Examples: Includes ready-to-adapt code for TypeScript (Next.js with Zod), Python (Django REST Framework), and Go (net/http), plus a pre-ship design checklist. - Use Case: When adding a new endpoint to a production API, activate this Skill to validate the URL structure, choose the right status codes, and generate a compliant error response format before writing code. ## Quick Start Review my new POST /api/v1/orders endpoint and check it against REST API design best practices for status codes, validation, and error responses.
