Slash Command

/design-api

Design REST API endpoints for a feature with URL structure, methods, request/response schemas, and error handling

npx claudepluginhub sagargupta16/claude-skills --plugin api-design

Prompt Preview

Design API endpoints for the specified feature or domain.

Steps:
1. Understand the feature requirements from the user's description
2. Identify the resources and their relationships
3. Detect the existing API framework (FastAPI, Express, Go, etc.) from the codebase
4. Check existing endpoints for naming and style conventions
5. Design endpoints following REST conventions:
   - Resource URLs (plural nouns, max 2 nesting levels)
   - HTTP methods (GET, POST, PUT, PATCH, DELETE)
   - Request body schemas
   - Response schemas with status codes
   - Error response format matching existing API ...

Command Content

Other plugins with /design-api

/design-api

1.0k

Designs RESTful or GraphQL API from project domain model and requirements, producing endpoint table with paths, request/response shapes, auth, and curl examples.

api-architect

/design-api

Complete REST/GraphQL API design with schema and resource modeling.

api-development

/design-api

Create API gateway and service contract specifications. Design scalable APIs.

system-design

/design-api

Create API contract (OpenAPI/GraphQL)

jm-adk

/design-api

RESTful API contract with auth, rate limits, pagination, error schema, and versioning

sde-system-design

/design-api

API contract design — OpenAPI, GraphQL, versioning, error handling

sovereign-architect

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitApr 5, 2026

Actions

View Source View Plugin View on GitHub View README

Design API endpoints for the specified feature or domain. Steps: 1. Understand the feature requirements from the user's description 2. Identify the resources and their relationships 3. Detect the existing API framework (FastAPI, Express, Go, etc.) from the codebase 4. Check existing endpoints for naming and style conventions 5. Design endpoints following REST conventions: - Resource URLs (plural nouns, max 2 nesting levels) - HTTP methods (GET, POST, PUT, PATCH, DELETE) - Request body schemas - Response schemas with status codes - Error response format matching existing API ...

Design API endpoints for the specified feature or domain.

Steps:

Understand the feature requirements from the user's description
Identify the resources and their relationships
Detect the existing API framework (FastAPI, Express, Go, etc.) from the codebase
Check existing endpoints for naming and style conventions
Design endpoints following REST conventions:
- Resource URLs (plural nouns, max 2 nesting levels)
- HTTP methods (GET, POST, PUT, PATCH, DELETE)
- Request body schemas
- Response schemas with status codes
- Error response format matching existing API patterns
- Pagination for list endpoints
Present the design as a table with URL, method, description, and request/response types
If approved, generate the route/controller code matching the project's patterns

Do NOT generate code until the user approves the design. Present the API contract first.