Design REST API contracts with resource naming, HTTP semantics, and response patterns.
npx skills add https://github.com/WUIX69/e-lock --skill api-design-wuix69
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/WUIX69/e-lock/tree/main/.agent/.agents/skills/api-design Command: npx skills add https://github.com/WUIX69/e-lock --skill api-design-wuix69
This Skill helps you design clear, consistent REST APIs that are easier for clients to use, safer to evolve, and simpler to maintain in production.
Ask for a review of your API draft and have the skill return a production-ready endpoint structure, status codes, error format, pagination strategy, and versioning guidance.
High-intent search queries and answers about installing and using this skill.
Designing a REST API with pagination, filtering, and sorting requires standardizing response envelopes, pagination metadata, and sparse fieldsets to ensure clients can query resources predictably and safely.
REST API validation failures and conflicts require choosing correct HTTP semantics for reads, writes, and deletions, applying safety-focused status code handling to standardize error payloads and client responses.
Structuring REST API endpoints for nested resources involves resource-oriented URL naming using clean, plural, kebab-case structures with sensible nesting for related resources to maintain consistency.
Versioning a REST API without breaking existing clients involves planning versioning strategies alongside authentication, authorization, and rate limiting to ensure safe evolution and production readiness.
Reviewing an existing REST API draft for production readiness involves turning endpoint sets into predictable contracts with standardized response patterns, error handling, and correct HTTP semantics.
A standardized REST API error payload format is needed to standardize response envelopes, ensuring safer API evolution, consistent client error handling, and simpler maintenance in production.
Design-System-ETDesign REST and GraphQL API architectures with OpenAPI 3.1 contracts.
jakubciszakDesign REST APIs for Symfony backends with OpenAPI specifications and DTO-based contracts.
thimsluggaGenerate API documentation with endpoints, schemas, and examples from source code.
qa-amanDefine and validate REST and GraphQL API contracts with schemas and versioning.
