What problem does it solve? Backend developers often ship APIs with inconsistent naming, ad-hoc error formats, missing pagination, and unplanned versioning, which creates maintenance burden and breaks client integrations. This Skill supplies a consolidated reference of production-grade API design patterns so endpoints, error responses, and validation follow consistent conventions. ## Core Features & Use Cases - RESTful Design Conventions: Resource naming, HTTP method mapping, status code selection, filtering, sorting, and URL versioning rules in lookup-table form. - Error & Pagination Standards: Standardized error response JSON with machine-readable codes and request IDs, plus offset and cursor-based pagination patterns. - Validation & Rate Limiting Checklists: Input validation methods (schema, regex, range, enum) mapped to tools like Zod, Joi, and pydantic, with rate limit targets and headers. - Use Case: When reviewing a new /users endpoint, an agent can verify naming conventions, confirm 422 responses include field-level error details, and check that list endpoints implement pagination before merge. ## Quick Start Ask the agent to review your API endpoint design against REST conventions for naming, status codes, error format, and pagination.
