Design REST APIs with versioning, pagination, filtering, and OpenAPI docs.
npx skills add https://github.com/bipinks/ghost-office --skill api-design-bipinks
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/bipinks/ghost-office/tree/main/.claude/skills/api-design Command: npx skills add https://github.com/bipinks/ghost-office --skill api-design-bipinks
Designing and implementing consistent REST APIs to prevent integration issues and governance drift across services.
Define a REST API design for a new service with versioned endpoints, consistent pagination and filtering, and an OpenAPI specification.
High-intent search queries and answers about installing and using this skill.
REST API design with versioning and pagination applies consistent conventions like versioned routes to enable scalable backend services. This approach standardizes APIs across microservices, preventing integration issues and governance drift.
HATEOAS improves REST API discoverability by including hyperlinks in responses, allowing clients to dynamically navigate services. Combined with OpenAPI documentation, it enhances client integration and standardizes interactions across microservices.
The best way to handle REST API errors is implementing structured error envelopes. This robust error handling mechanism ensures consistent error reporting across services, preventing integration issues and improving client integration.
Yes, this REST API design approach applies to backend services of varying sizes, including both monoliths and microservices. It ensures consistent conventions for versioning, filtering, and rate limiting across different service architectures.
Generate OpenAPI documentation for a new service by defining a REST API design with versioned endpoints, consistent pagination, and filtering. This improves client discoverability and integration while ensuring secure API documentation across frameworks.
Rate limiting is needed in REST API design to control traffic and protect backend services from overload. It is a core feature of robust API governance, ensuring scalable and consistent service availability across microservices.
RasmusGodskeEnforce PHP/Laravel backend conventions across controllers, models, services, and tests.
Dokkabei97Design API contracts with OpenAPI and GraphQL schemas.
Prathmesh2000Design API gateways with routing, authentication, and rate limiting.
Camilo8902Migrate REST APIs to GraphQL incrementally using schema stitching and REST data source wrappers.
