fastapi-service-development
Fastapi Service Development
Overview
Use this skill to build FastAPI services with explicit schema contracts, controlled dependency lifecycles, and predictable async runtime behavior.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Dependency lifecycle guidance:
references/fastapi-dependency-lifecycle-guidance.md
- Schema contract guidance:
references/fastapi-schema-contract-guidance.md
Templates And Assets
- Router implementation starter:
assets/fastapi-router-template.py
- Error response shape template:
assets/fastapi-error-model-template.json
- Service verification checklist:
assets/fastapi-service-checklist.md
Inputs To Gather
- Endpoint definitions and request/response schema requirements.
- Dependency injection graph and external service dependencies.
- Authentication, validation, and observability requirements.
- Async I/O boundaries and expected latency constraints.
- Internal service DTO contracts to avoid untyped
dict[str, Any]propagation.
Deliverables
- Endpoint map with typed request/response models.
- Dependency and lifecycle management plan.
- Error contract and exception handling policy.
- Verification checklist and test focus areas.
Workflow
- Define Pydantic models and endpoint contracts first.
- Separate routers, service logic, and infrastructure adapters.
- Convert boundary payloads to explicit domain input/output models before service-layer execution.
- Manage shared resources using
references/fastapi-dependency-lifecycle-guidance.md. - Implement exception mapping with
assets/fastapi-error-model-template.json. - Validate behavior and docs with
assets/fastapi-service-checklist.md.
Quality Standard
- All endpoints expose explicit typed schemas.
- Dependency scope and teardown behavior are deterministic.
- Error responses are stable and machine-parseable.
- OpenAPI output reflects actual runtime behavior.
- Internal logic minimizes runtime casts by using precise models at boundaries.
Failure Conditions
- Stop when schema contracts are ambiguous or loosely typed.
- Stop when async request paths contain hidden blocking I/O.
- Escalate when dependency lifecycle cannot be managed safely.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9