What problem does it solve? Inconsistent REST API design leads to confusing endpoints, wrong HTTP status codes, missing pagination, and error responses that leak internals or confuse client developers. This Skill provides a complete set of conventions so every endpoint follows the same predictable patterns. ## 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 header, 422 for validation, 429 for rate limits). - Pagination, Filtering, and Sorting: Covers offset-based and cursor-based pagination, bracket-notation filters, multi-field sorting, and sparse fieldsets. - Standardized Error and Response Envelopes: Defines JSON response shapes for success, collections, and field-level validation errors, plus rate-limit headers and versioning strategy. - Use Case: When adding a new endpoint to a Next.js, Django REST Framework, or Go service, apply the checklist to validate naming, status codes, auth, and rate limiting before shipping. ## Quick Start Use the api-design skill to review my new /api/v1/orders endpoint and check it against REST conventions.
