api-design-patterns
REST API design with resource naming, pagination, versioning, and OpenAPI spec generation
Profile →npx skills add rohitg00/awesome-claude-code-toolkit --skill api-design-patterns --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 Design Patterns ## Resource Naming - Use plural nouns: `/users`, `/orders`, `/products` - Nest for relationships: `/users/{id}/orders` - Max nesting depth: 2 levels. Beyond that, use query params or top-level resources - Use kebab-case: `/user-profiles`, not `/userProfiles` - Never put verbs in URLs: `/users/{id}/activate` is wrong, use `POST /users/{id}/activation` ## HTTP Methods | Method | Purpose | Idempotent | Request Body | Success Code | |--------|---------|------------|-------------|-------------| | GET | Read resource(s) | Yes | No | 200 | | POST | Create resource | No | Yes | 201 | | PUT | Full replace | Yes | Yes | 200 | | PATCH | Partial update | No | Yes | 200 | | DELETE | Remove resource | Yes | No | 204 | Return `Location` header on POST with the URL of the created resource. ## Status Codes ``` 200 OK - Successful read/update 201 Created - Successful creation 204 No Content - Successful delete 400 Bad Request - Validation error (include field-level errors) 401 Unauthorized - Missing or invalid authentication 403 Forbidden - Authenticated but not authorized 404 Not Found - Resource does not exist 409 Conflict - State conflict (duplicate, version mismatch) 422 Un
- Resource Naming
- HTTP Methods
- Status Codes
- Error Response Format
- Cursor-Based Pagination (preferred)
- Offset-Based Pagination (simple cases only)
- Filtering and Sorting
- Versioning
- Request/Response Headers
- OpenAPI Spec Guidelines
- Rate Limiting Strategy
What does the api-design-patterns skill do?
REST API design with resource naming, pagination, versioning, and OpenAPI spec generation
How do I install it?
Run `npx skills add rohitg00/awesome-claude-code-toolkit --skill api-design-patterns --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 rohitg00/awesome-claude-code-toolkit, a repository with 2,438 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.