Define REST API patterns for naming, status codes, pagination, and versioning.
npx skills add https://github.com/sbalagan22/bloomr --skill api-design-sbalagan22
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/sbalagan22/bloomr/tree/main/.claude/skills/api-design Command: npx skills add https://github.com/sbalagan22/bloomr --skill api-design-sbalagan22
REST API design often suffers from inconsistent naming, poor error handling, and confusing versioning, making contracts hard to maintain and hard to onboard new developers.
Provide a clean, production-ready API design blueprint for a new service that follows the conventions above.
High-intent search queries and answers about installing and using this skill.
REST API design patterns standardize resource naming using kebab-case plural endpoints and define standard error envelopes with consistent codes. This ensures predictable contracts, making production services easier to maintain and onboard new developers.
Design REST API pagination and filtering by applying scalable patterns like offset and cursor-based approaches. This provides a consistent syntax for sorting and retrieving large datasets without overwhelming production services.
Use correct HTTP semantics by mapping GET, POST, PUT, PATCH, and DELETE methods to meaningful status code responses. This ensures clear communication of API operation results and predictable behavior across resource endpoints.
Implement REST API versioning and rate limiting by following explicit versioning guidance and rate limiting specifications. This delivers clear contracts and predictable errors for public SaaS product endpoints.
Yes, you can apply these REST API design rules to audit existing API contracts. The concrete naming rules, status codes, and error response formats drive consistent behavior and design reviews across production services.
armanzeroeightDesign RESTful API endpoints with resource models, HTTP methods, and URL structures.
kmshihab7878Enforce consistent API design frameworks across REST, GraphQL, and OpenAPI specifications.
derekhu0002Standardize REST API design for resource naming, HTTP methods, and status codes.
ekremmkasapDesign REST and GraphQL API principles with schema-first templates.
