API Design

When to Use

• Designing new API endpoints or schemas
• Reviewing existing API contracts for consistency
• Choosing between REST and GraphQL for a project
• Planning versioning, pagination, or error handling strategies
• Creating or reviewing OpenAPI/GraphQL specifications
• Naming URIs, fields, or resources
• Reviewing API security posture

When NOT to use:

• Framework-specific implementation details (though FastAPI patterns are available as a secondary reference below)
• Database schema design (unless it directly affects the API contract)
• Frontend data fetching code (unless reviewing the API contract it consumes)

Invocation Notice