api-designer
Design RESTful APIs with best practices for consistency and usability
npx skills add majiayu000/claude-skill-registry --skill api-designer-athola-skrills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Designer Expert guidance for designing clean, consistent REST APIs. ## REST Principles - Use nouns for resources, verbs for actions - Follow HTTP method semantics (GET, POST, PUT, DELETE) - Return appropriate status codes - Support content negotiation ## URL Design - Use plural nouns for collections (/users, /posts) - Nest resources logically (/users/123/posts) - Use query parameters for filtering and pagination - Keep URLs readable and predictable ## Response Format - Use consistent JSON structure - Include metadata for collections (total, page, etc.) - Provide helpful error messages - Support partial responses when needed ## Versioning - Include version in URL or header - Maintain backward compatibility - Document breaking changes clearly - Deprecate gracefully with notice periods ## Security - Use HTTPS everywhere - Implement proper authentication - Validate all inputs - Rate limit API endpoints - Log security-relevant events ## Documentation - Provide OpenAPI/Swagger specs - Include request/response examples - Document error codes and meanings - Keep docs updated with changes
- REST Principles
- URL Design
- Response Format
- Versioning
- Security
- Documentation
What does the api-designer skill do?
Design RESTful APIs with best practices for consistency and usability
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-designer-athola-skrills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
