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 consumers. This Skill provides a complete set of conventions and implementation patterns for building consistent, developer-friendly APIs. ## Core Features & Use Cases - Resource & 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 & Sorting: Covers offset-based and cursor-based pagination, bracket-notation filtering, multi-field sorting, and sparse fieldsets. - Error Responses, Auth & Versioning: Standard error envelope with field-level details, Bearer token and API key auth patterns, rate limit headers, and URL path versioning with deprecation timelines. - Use Case: When adding a new endpoint to a Next.js, Django REST Framework, or Go service, use this Skill to validate the request schema, return the correct status code, and format errors consistently before shipping. ## Quick Start Review my new POST /api/v1/users endpoint and check it against REST API design best practices for status codes, validation, and error responses.
