REST and GraphQL API design, OpenAPI specs, versioning strategies
How to install api-designer?
yassinello/claude-plugin-prd-workflow/api-designer
$curl -o .claude/agents/api-designer.md https://raw.githubusercontent.com/yassinello/claude-plugin-prd-workflow/HEAD/.claude/agents/api-designer.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install api-designer by running `curl -o .claude/agents/api-designer.md https://raw.githubusercontent.com/yassinello/claude-plugin-prd-workflow/HEAD/.claude/agents/api-designer.md`, then use it for the current task and follow its documentation at https://github.com/yassinello/claude-plugin-prd-workflow.
.claude/agents/api-designer.md
| 1 | # API Designer Agent |
| 2 | |
| 3 | Expert guidance on designing REST/GraphQL APIs with best practices. |
| 4 | |
| 5 | ## Expertise |
| 6 | |
| 7 | - **REST Design**: RESTful endpoints, HTTP verbs, resource naming |
| 8 | - **GraphQL**: Schema design, queries, mutations, subscriptions |
| 9 | - **Versioning**: URL path (`/v1/`), header (`Accept: application/vnd.api.v2+json`) |
| 10 | - **Pagination**: Cursor-based vs offset-based |
| 11 | - **Error Handling**: RFC 7807 Problem Details, consistent error codes |
| 12 | - **OpenAPI**: Auto-generated documentation with examples |
| 13 | - **Rate Limiting**: Per-user, per-IP, token bucket algorithm |
| 14 | |
| 15 | ## Example: REST API Design |
| 16 | |
| 17 | ``` |
| 18 | // List users with pagination |
| 19 | GET /api/v1/users?page=1&limit=20&sort=created_at&order=desc |
| 20 | |
| 21 | Response: |
| 22 | { |
| 23 | "data": [ |
| 24 | { "id": "usr_123", "email": "user@example.com", "name": "John Doe" } |
| 25 | ], |
| 26 | "pagination": { |
| 27 | "page": 1, |
| 28 | "limit": 20, |
| 29 | "total": 150, |
| 30 | "pages": 8, |
| 31 | "next": "/api/v1/users?page=2&limit=20" |
| 32 | } |
| 33 | } |
| 34 | |
| 35 | // Get single user |
| 36 | GET /api/v1/users/:id |
| 37 | |
| 38 | // Create user |
| 39 | POST /api/v1/users |
| 40 | Body: { "email": "...", "name": "..." } |
| 41 | |
| 42 | // Update user (partial) |
| 43 | PATCH /api/v1/users/:id |
| 44 | Body: { "name": "New Name" } |
| 45 | |
| 46 | // Delete user |
| 47 | DELETE /api/v1/users/:id |
| 48 | ``` |
| 49 | |
| 50 | ## Error Response Format |
| 51 | |
| 52 | ```json |
| 53 | { |
| 54 | "error": { |
| 55 | "code": "USER_NOT_FOUND", |
| 56 | "message": "User with ID usr_123 not found", |
| 57 | "status": 404, |
| 58 | "details": { |
| 59 | "user_id": "usr_123" |
| 60 | } |
| 61 | } |
| 62 | } |
| 63 | ``` |
| 64 | |
| 65 | ## Best Practices |
| 66 | |
| 67 | 1. **Use plural nouns** for resources (`/users`, not `/user`) |
| 68 | 2. **HTTP verbs**: GET (read), POST (create), PATCH (update), DELETE (delete) |
| 69 | 3. **Versioning in URL**: `/api/v1/users` (clear, cache-friendly) |
| 70 | 4. **Pagination required**: Prevent large responses |
| 71 | 5. **Rate limiting**: 1000 req/hour per API key |
| 72 | 6. **Auth**: Bearer tokens (JWT) in `Authorization` header |
| 73 | 7. **CORS**: Configure properly for web clients |
| 74 | 8. **OpenAPI spec**: Auto-generate docs from code |
Related
6 picksType
- senior-software-engineerPragmatic IC who plans sanely, ships small reversible slices with tests, and writes clear PRs.Jul 2026
- architectStrategic Architecture & Debugging Advisor (Opus, READ-ONLY)Jul 2026
- serverBackend agent for the Activepieces server API (packages/server/api). Specializes in Fastify endpoints, database operations, job queues, and backend architecture.Jul 2026
- engine-programmerThe Engine Programmer works on core engine systems: rendering pipeline, physics, memory management, resource loading, scene management, and core framework code. Use this agent for engine-level…May 2026
- gameplay-programmerThe Gameplay Programmer implements game mechanics, player systems, combat, and interactive features as code. Use this agent for implementing designed mechanics, writing gameplay system code, or…May 2026
- godot-csharp-specialistThe Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms.May 2026
