Standardize REST API resource naming, status codes, and error formats.
npx skills add https://github.com/its-Basudeba/Care-HMS --skill api-design-its-basudeba
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/its-Basudeba/Care-HMS/tree/main/.agent/.agents/skills/api-design Command: npx skills add https://github.com/its-Basudeba/Care-HMS --skill api-design-its-basudeba
This skill addresses the inconsistency and technical debt often found in API development by providing a standardized framework for resource naming, status code usage, and error handling.
Use the api-design skill to generate a RESTful endpoint structure for a new user management module.
High-intent search queries and answers about installing and using this skill.
Standardize REST API architecture by defining consistent pluralized, kebab-case resource naming, HTTP status code semantics, and error response formats. This ensures endpoints follow industry-standard RESTful practices for microservices, making APIs intuitive for frontend developers.
Structure REST API pagination and filtering by defining consistent envelope formats for success and pagination states. This approach facilitates scalable endpoint design and ensures technical compliance with RESTful principles in production environments.
REST API error response formats should be defined using standardized envelopes that ensure technical compliance with RESTful principles. This framework provides clear rules for error states, making the API contract documentation developer-friendly.
Yes, this REST API design approach supports sub-resource relationships and versioning strategies. It provides clear rules for URL structures and facilitates scalable endpoint design for production environments.
You need to standardize HTTP status code semantics when building a new backend module to address inconsistency and technical debt. This framework provides a standardized approach for resource modeling and response formats.
Inconsistent REST API naming creates technical debt by failing to provide clear rules for sub-resource relationships and URL structures. Standardizing resource modeling and technical compliance ensures scalable endpoints and developer-friendly API contracts.
michaelsvanbeekDefine REST API design patterns and contract standards for endpoints and OpenAPI documentation.
thimsluggaGenerate API documentation with endpoints, schemas, and examples from source code.
hyukudanDesign RESTful and GraphQL APIs with resource modeling and error handling patterns.
Camilo8902Migrate REST APIs to GraphQL incrementally using schema stitching and REST data source wrappers.
