add-endpoint

To add a FastAPI endpoint, you provide the HTTP method, path, and description, then scaffold the route by following existing project conventions for imports, error handling, and response formats to ensure consistency.

You maintain consistent FastAPI error handling by analyzing existing routers and app registration patterns before scaffolding, ensuring new routes mirror established import styles and response shapes to reduce integration issues.

The best way to scaffold a FastAPI CRUD route is to review current code conventions first, then generate the new endpoint with matching validation, error handling, and testing patterns to prevent breaking existing API shapes.

You write tests for a new FastAPI endpoint by following the testing guidance provided during scaffolding, which instructs you to review and align with the repository's established testing patterns before implementation.

Yes, the scaffolding approach works with existing FastAPI routers by performing pattern discovery on current app registration and routing conventions to mirror imports, error handling, and response formats.

New FastAPI endpoints become inconsistent when code generation skips reviewing existing routers first, leading to misaligned import styles, error handling, and response formats that break project conventions.