From devloop
Provides REST and GraphQL API design best practices for URL structures, endpoints, versioning, pagination, error responses, and HTTP status codes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devloop:api-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
REST API design best practices.
REST API design best practices.
GET /users # List
GET /users/:id # Get one
POST /users # Create
PUT /users/:id # Replace
PATCH /users/:id # Update
DELETE /users/:id # Delete
/api/v1/users # URL versioning
Accept: application/vnd.api.v1+json # Header
{
"data": [...],
"pagination": {
"page": 1,
"per_page": 20,
"total": 100,
"total_pages": 5
}
}
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid email format",
"details": [{"field": "email", "issue": "invalid format"}]
}
}
| Code | Use |
|---|---|
| 200 | Success |
| 201 | Created |
| 400 | Bad request |
| 401 | Unauthorized |
| 404 | Not found |
| 500 | Server error |
npx claudepluginhub zate/cc-plugins --plugin devloopGuides REST and GraphQL API design including endpoint structure, error handling, versioning, and documentation. Best for new APIs or contract reviews.
Designs RESTful APIs and GraphQL schemas following best practices for endpoints, request/response schemas, and architecture.
Guides API design decisions including REST vs GraphQL, resource modeling, versioning, error contracts, pagination, and authentication patterns.