
Rest Api Design Advisor
Design scalable REST APIs with OpenAPI 3.0 and Swagger documentation
What You Can Do
You can design complete REST API specifications from requirements, translating them into resource-oriented endpoint architectures that follow industry best practices. Claude generates OpenAPI 3.0 schemas with validated request/response definitions, ensures correct HTTP method semantics and status code usage, and produces Swagger documentation ready for Swagger UI, ReDoc, or Postman integration. Catch design anti-patterns and naming inconsistencies before implementation.
Features
translates requirements into RESTful URL hierarchies and structures
creates complete, valid specifications with request/response models
ensures GET, POST, PUT, PATCH, DELETE usage matches RESTful semantics
applies correct HTTP status codes (200, 201, 400, 401, 403, 404, 422, 500, etc.) to each endpoint
enforces consistent resource names, parameter naming, and URI patterns
produces interactive API documentation for teams and client developers
identifies design violations and suggests corrections before deployment
includes standard patterns for querying collections
Example Output
Example 1: E-commerce Product API Design
Paths:
/products:
GET: List all products with pagination
POST: Create new product (201 Created)
/products/{id}:
GET: Retrieve single product (200 OK)
PUT: Update product (200 OK)
DELETE: Remove product (204 No Content)
Status Codes: 400 Bad Request, 401 Unauthorized, 404 Not Found, 422 Unprocessable Entity
Example 2: User Management API
Endpoint: POST /users
Request: {name, email, role}
Response 201: {id, name, email, role, created_at}
Response 400: {error, field, message}
Response 409: {error: "Email already exists"}
Example 3: OpenAPI 3.0 Specification Generated YAML with complete schemas, security definitions, error responses, and documentation ready for Swagger UI or code generation.
What's Included
- SKILL.md instruction file with REST API design methodology:
- OpenAPI 3.0 template with complete specification structure:
- Endpoint design checklist covering HTTP methods, status codes, and naming conventions:
- Common API patterns for pagination, filtering, sorting, and error handling:
- Swagger documentation template ready for Swagger UI or ReDoc integration:
Who It's For
- Backend Engineers designing new microservices or API endpoints
- API Architects establishing consistent patterns across service ecosystems
- Technical Leads reviewing endpoint design quality and governance
- DevOps/Platform Engineers standardizing API specifications across teams
- Full-Stack Developers building APIs that clients will consume
Best For
- Greenfield API design — architecting new services from requirements
- API refactoring — modernizing legacy endpoints to REST standards
- OpenAPI specification generation — creating formal docs for Swagger UI or code generation
- Team API guidelines — establishing consistent endpoint patterns and naming
- Design review and validation — catching anti-patterns before implementation






