fastapi-backend
Skill1 starsChanged 11 months agoMITView on GitHub
Develop FastAPI services with SQLAlchemy models, Pydantic schemas, async handlers, and proper error handling. Use when building API endpoints, creating routers, implementing database models, or working with backend/services/ files.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- JameMy0001/antigravity-skills-hubtheir own version, first seen Oct 2, 2026
- cohen-liel/hivemindtheir own version, first seen Mar 17, 2026
- anasahmed07/doittheir own version, first seen Jan 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- cohen-liel/hivemind★ 108same name
- anasahmed07/doit★ 1same name
- JameMy0001/antigravity-skills-hub★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llm-integrationSkill
- nextjs-frontendSkill
- project-documentationSkill
- python-testingSkill
- security-reviewSkill
- sqlalchemy-databaseSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Use async/await for all I/O operations
- Distinctive: line 54
Use specific HTTPException status codes
- Very specific: line 57
Use body for request body schemas (not request)
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
FastAPI Backend Development
ETPS Architecture
- FastAPI with async/await patterns
- SQLAlchemy ORM for database models (backend/db/models.py)
- Pydantic schemas (backend/schemas/)
- Service layer pattern (backend/services/)
- Config loaded from backend/config/config.yaml
Key Files
backend/main.py- Application entry pointbackend/routers/- API endpoint definitionsbackend/services/- Business logicbackend/schemas/- Pydantic request/response modelsbackend/db/models.py- SQLAlchemy ORM models
Service Structure Pattern
from pydantic import BaseModel, Field
from fastapi import APIRouter, HTTPException, Depends, status
from sqlalchemy.orm import Session
from db.database import get_db
router = APIRouter()
@router.post("/endpoint", response_model=ResponseSchema, status_code=status.HTTP_200_OK)
async def my_endpoint(
request: Request, # Must be named 'request' for rate limiter
body: RequestSchema,
db: Session = Depends(get_db)
):
# Implementation
return resultKey Services
| Service | Purpose |
resume_tailor.py | Resume generation orchestrator |
cover_letter.py | Cover letter with critic loop |
critic.py | Quality evaluation (ATS, style) |
skill_gap.py | Semantic skill matching |
job_parser.py | Job description parsing |
llm/ | LLM abstraction layer |
Best Practices
- Use async/await for all I/O operations
- Validate input with Pydantic schemas with Field constraints
- Use specific HTTPException status codes
- Load config from config.yaml (not hardcoded)
- Rate limiter requires parameter named exactly
request - Use
bodyfor request body schemas (notrequest)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

