api-design

REST API design follows standard conventions for naming endpoints, selecting HTTP methods, and returning status codes to ensure developer-friendliness. This Skill provides patterns to standardize endpoint structure and consistency across your new API.

API versioning can be implemented using URL path, header, or content negotiation strategies. This Skill provides design patterns to help you choose and apply the appropriate versioning scheme for your framework requirements.

RFC 9457 Problem Details standardizes API errors by providing a machine-readable format for error responses. This Skill helps you implement this specification to ensure consistent, developer-friendly error reporting across endpoints.

Yes, you can use this Skill to generate an OpenAPI specification for your new API. It provides comprehensive design patterns for endpoint structure, versioning, and errors that translate directly into OpenAPI documentation.

Yes, this Skill supports designing GraphQL schemas alongside REST conventions and gRPC services. It provides comprehensive patterns to structure your GraphQL framework design with consistent best practices.

Content negotiation versioning is suitable when you want to keep URLs clean, while URL path versioning offers explicit visibility. This Skill provides design patterns to evaluate and implement the best strategy for your API.