Design REST APIs with patterns for naming, status codes, pagination, and versioning.
npx skills add https://github.com/cncoder/oneclaw --skill api-design-cncoder
Please help me install this Agent Skill. Skill: api-design Source: https://github.com/cncoder/oneclaw/tree/main/skills/api-design Command: npx skills add https://github.com/cncoder/oneclaw --skill api-design-cncoder
REST API design patterns help teams build consistent, scalable interfaces by standardizing resource naming, responses, and versioning.
Run a design audit of your existing API contracts and apply the patterns to a new endpoint.
High-intent search queries and answers about installing and using this skill.
To design REST APIs that scale cleanly, standardize resource naming with kebab-case and plural nouns, apply correct HTTP semantics, and implement robust pagination, error handling, and versioning strategies.
Handle REST API pagination and filtering by applying standardized lifecycle patterns that support sorting and slicing large datasets, ensuring consistent response formats and clear URL conventions for nested resource relationships.
Your REST API should use standardized HTTP status codes alongside structured error schemas and response envelopes to clearly communicate failures, ensuring clients receive consistent, predictable error handling across all endpoints.
Implement REST API versioning and rate limiting by applying lifecycle patterns that manage endpoint changes securely over time, protecting production services from abuse while maintaining backward compatibility for existing clients.
Yes, you can run a design audit against your existing API contracts to check resource naming, HTTP semantics, and security considerations, applying the patterns to refactor endpoints and document errors effectively.
Consistent REST API resource naming matters because using plural nouns and kebab-case endpoints creates clear, predictable URL conventions that make interfaces easier to consume, scale, and maintain across development teams.
pkuppensEnforce REST conventions, versioning, and OpenAPI documentation for API endpoints.
gridi-aiGenerate OpenAPI 3.0 specifications from tech specs for REST APIs.
cenjieSecure REST APIs with authentication, rate limiting, CORS, and input validation.
iludeDesign REST and GraphQL APIs with language-agnostic patterns for routes, schemas, and specs.
