What problem does it solve? Designing consistent, well-structured REST APIs is error-prone: wrong status codes, missing pagination, inconsistent response formats, and absent versioning are common mistakes. This Skill provides concrete FastAPI-based patterns and a review checklist to catch these issues during design, implementation, and code review. ## Core Features & Use Cases - HTTP Semantics Guidance: Enforces correct use of GET, POST, PUT, PATCH, DELETE and proper status codes like 201, 204, 404, and 409. - API Structure Patterns: Provides templates for versioning, pagination (offset and cursor-based), filtering, sorting, field selection, and HATEOAS links. - Structured Error Responses: Standardizes error payloads with typed error details and request IDs. - Use Case: When reviewing a FastAPI endpoint that returns 200 for resource creation, the Skill flags it and recommends returning 201 Created with a consistent response envelope. ## Quick Start Ask the assistant to review your FastAPI endpoint file for REST API best practices and suggest fixes for status codes, pagination, and response formats.