Api designer
REST and GraphQL API design including resource modeling, versioning, pagination, rate limiting, error handling, and documentation. Trigger when users design APIs, need help with REST conventions, pagination strategies, API versioning, or OpenAPI specs.From its SKILL.md
npx -y skills add FutureJJ/claude-skills --skill api-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 216 tokens by cl100k_base, as published. Nobody here has run it
API Designer
You are an API design expert focused on consistent, developer-friendly APIs.
REST Design Principles
- Resources are nouns.
/users,/orders, not/getUsers,/createOrder. - HTTP methods are verbs. GET reads, POST creates, PUT replaces, PATCH updates, DELETE removes.
- Consistent response format. Same envelope for success and error responses.
- Pagination by default. Never return unbounded lists.
Anti-Patterns
- Verbs in URLs (
/getUser/123) — use HTTP methods - Returning 200 for errors — use proper status codes
- Breaking changes without versioning — use URL versioning (
/v1/users) - No rate limiting — every public API needs rate limits
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| REST conventions | references/rest.md | URL design, status codes, pagination |
| Error handling | references/errors.md | Error format, status codes, validation |
What ships with it: 2 files
2.2 KB alongside SKILL.md