Design and validate REST APIs with consistent WrongStack conventions.
npx skills add https://github.com/WrongStack/WrongStack --skill api-design-wrongstack
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/api-design Command: npx skills add https://github.com/WrongStack/WrongStack --skill api-design-wrongstack
REST API design and reviews for WrongStack, ensuring consistency, correctness, and scalable conventions across services.
Draft or review a REST API plan for a new resource applying the standard status codes, error shapes, and pagination rules.
High-intent search queries and answers about installing and using this skill.
Design a REST API with consistent error handling by enforcing conventional HTTP status codes (200, 201, 400, 401, 403, 404, 500) alongside uniform error shapes. This ensures predictable error bodies and correct response semantics across all service endpoints.
Cursor-based pagination is a REST API navigation method using a pointer to fetch subsequent result sets rather than offsets. Apply it to resource collections to ensure consistent performance and stable data retrieval during real-time inserts.
The best way to version REST APIs and handle breaking changes is prefixing routes with version paths. This practice isolates breaking changes from existing clients, preserving backward compatibility while rolling out new resource contracts.
Implement server-side validation in a REST API by enforcing data constraints on the server and returning uniform error shapes containing clear field errors. This provides clients with specific validation feedback for invalid request payloads.
Yes, you can audit existing REST API contracts and refactor endpoints by checking them against established conventions. This process reviews resource naming, pagination rules, and security practices to ensure service-wide consistency.
REST API resource naming should use plural nouns to maintain uniform shapes and standardize endpoint paths. This convention aligns with collection-level routing, ensuring predictable interactions across all services.
nicholasgriffintnPlan backend systems, APIs, and data models with structured architecture decisions.
AZANIRGenerate OpenAPI 3.x specifications and detect breaking changes from API sources.
cenjieSecure REST APIs with authentication, rate limiting, CORS, and input validation.
act70255Provide design principles and patterns for RESTful and GraphQL APIs.
