Design REST and GraphQL APIs with consistent naming, pagination, and versioning standards.
npx skills add https://github.com/BryantChi/webdev-skills --skill api-bryantchi
Please help me install this Agent Skill. Skill: API 設計技能 Source: https://github.com/BryantChi/webdev-skills/tree/main/api Command: npx skills add https://github.com/BryantChi/webdev-skills --skill api-bryantchi
Designing scalable, consistent APIs to reduce integration friction and maintenance costs.
Create a consistent REST/GraphQL API design by applying these guidelines.
High-intent search queries and answers about installing and using this skill.
To design consistent REST and GraphQL APIs for microservices, apply standardized endpoint naming, pagination, filtering, and authentication conventions. This reduces integration friction and maintenance costs across teams and platforms.
The best way to implement API versioning and authentication standards is to enforce consistent conventions across all public APIs and backend services. Standardized responses and error handling further improve maintainability.
API endpoint naming for REST and GraphQL schemas works by applying consistent conventions across all services. This ensures scalable design, standardized responses, and proper status codes for frontend integration.
Yes, you can use these API design conventions for public APIs across different teams. The guidelines enforce endpoint naming, versioning, and authentication standards specifically to align microservices and public APIs.
API design needs standardized error handling and status codes to reduce integration friction and maintenance costs. Consistent responses across REST and GraphQL endpoints ensure maintainable backend services.
kernex-devDesign backend APIs, data models, and service architectures with endpoint contracts and auth rules.
hffmnnjGenerate API reference documentation from OpenAPI specs and GraphQL schemas.
notqueValidate API endpoint responses, timing, and JSON keys from endpoints.json.
alexsandrocruzDesign REST APIs with resource-oriented naming, HTTP methods, status codes, and versioning.
