FastAPI REST API Design

Use this skill when designing, implementing, or reviewing FastAPI REST endpoints.

Purpose and scope

This skill enforces practical REST design and FastAPI implementation quality: resource naming, HTTP semantics, schema quality, dependency boundaries, security checks, and concise review output.

Core design rules

Resource and path conventions

• Use nouns in paths, not action verbs.
• Use plural collection names such as /projects, /users.
• Use stable item identifiers such as /projects/{project_id}.
• Keep names lowercase and consistent.
• Keep nesting shallow (typically max 2 levels), for example /projects/{project_id}/models.
• Do not expose internal storage structure in public routes.