Rewrites Tailwind HTML to standalone CSS files preserving classes and visual output.
npx skills add https://github.com/Levironexe/architect --skill fastapi-levironexe
Please help me install this Agent Skill. Skill: FastAPI Source: https://github.com/Levironexe/architect/tree/main/skills/stacks/fastapi Command: npx skills add https://github.com/Levironexe/architect --skill fastapi-levironexe
Unstructured or “vibe-coded” FastAPI projects become hard to maintain, test, and evolve because HTTP handlers, business logic, validation schemas, and persistence concerns are mixed together in the wrong places.
Ask your coding agent to reorganize each feature domain into {domain}/router.py, {domain}/service.py, {domain}/schemas.py, {domain}/models.py, and {domain}/dependencies.py, then update main.py to register routers with consistent prefixes and tags.
High-intent search queries and answers about installing and using this skill.
Refactoring a FastAPI project to domain driven design involves separating HTTP routing from business orchestration and persistence by co-locating router, service, schemas, models, and dependencies files per feature domain to enforce clear responsibility boundaries.
FastAPI service layers contain HTTP request handling when business logic and routing are mixed together, violating responsibility boundaries. Applying a domain-driven architecture moves orchestration to service layers without HTTP knowledge, keeping routers thin with Pydantic validation and Depends injection.
The best way to separate SQLAlchemy models from Pydantic schemas in FastAPI is to enforce explicit request and response contracts. This uses separate Pydantic input and output schemas so the API contract is decoupled from SQLAlchemy ORM models within a domain-driven folder structure.
Yes, you can incrementally refactor a multi-domain REST API by co-locating router, service, schemas, models, and dependencies per feature domain. This domain-driven separation reduces cross-file confusion and supports safe phased improvements without breaking existing FastAPI endpoints.
In a FastAPI DDD architecture, you should centralize configuration settings in a dedicated config module and isolate DB session wiring in a database module. Dependency injection logic via Depends should be placed in a separate dependencies module to enforce dependency and configuration discipline.
You need to restructure your FastAPI codebase into a domain-driven architecture when unstructured projects mix HTTP handlers, business logic, validation schemas, and persistence concerns together, making the application hard to maintain, test, and evolve across multi-domain REST APIs.
adelabdelgawadGenerate FastAPI CRUD modules with routers, services, repositories, schemas, and models.
jholhewresGenerate CHANGELOG.md files by parsing Git conventional commits.
olehsvyrydovBuild FastAPI backends with async endpoints, Pydantic v2 models, and SQLAlchemy async ORM.
carlopezzutoApply Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to backend systems.
