What problem does it solve? Inconsistent API design leads to confusing endpoints, wrong HTTP status codes, and fragile integrations that frustrate developers consuming your API. This Skill provides a complete set of REST API design conventions so every endpoint follows predictable, production-grade patterns. ## Core Features & Use Cases - Resource and URL Conventions: Enforces plural, kebab-case, noun-based resource naming with correct HTTP method semantics and status code usage. - Pagination, Filtering, and Sorting: Covers offset and cursor pagination strategies, bracket-notation filtering, multi-field sorting, and sparse fieldsets. - Error Responses, Auth, Rate Limiting, and Versioning: Standard error envelope formats, Bearer token and API key patterns, rate limit headers and tiers, and URL path versioning with deprecation timelines. - Use Case: When adding a new orders endpoint to a Laravel or Next.js backend, use this Skill to define the URL structure, validation error format, cursor pagination, and 201 Created response with a Location header. ## Quick Start Use the api-design skill to design a paginated REST endpoint for managing orders with proper status codes and error responses.