M
martinDTV/claude-fastapi-architect-skill
Claude Code skill for FastAPI backends that picks the right architecture for each project, from prototype to…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · martinDTV/claude-fastapi-architect-skill · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-28 · last seen 2026-11-14 · seen 19× · listed by 2 sources
- Score
- score 203 · 2 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
martinDTV/claude-fastapi-architect-skill;first catalogued 2026-10-28;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# fastapi-architect
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A Claude Code skill that gives FastAPI projects the right amount of architecture: it chooses between a prototype, a modular monolith, ports and adapters, or microservices based on the project's actual requirements, enforces module boundaries mechanically, and applies production code standards.
> 🇲🇽 Español más abajo.
## Why another FastAPI skill
Most FastAPI skills either teach framework syntax or impose one architecture (usually full Clean Architecture with a DI container) on every project. Both fail in practice: a CRUD API wrapped in five layers is as costly as a 40-endpoint main.py.
This skill instead:
Right-sizes the architecture. Four stages, with explicit signals for moving between them. The default for production work is a modular monolith; ports and adapters are applied per module, only where the domain needs them.
Knows when a monolith should become microservices, and when it should not. It applies hard criteria (independent scaling, team ownership, release coupling, isolation, runtime needs) plus prerequisites, and pushes back when a split would produce a distributed monolith. When extraction is justified, it follows a strangler-fig playbook.
Enforces boundaries with tooling, not good intentions. import-linter contracts make cross-module imports and layer violations fail CI.
Ships verified code. Every snippet in the references passes ruff, mypy --strict and import-linter, and the example module's tests pass against PostgreSQL with current FastAPI, Starlette, SQLAlchemy 2.x and Pydantic v2, with warnings treated as errors.
Uses progressive disclosure. SKILL.md holds the decision workflow; detailed references load only when the task needs them.
## Install
### As a Claude Code plugin (recommended)
/plugin marketplace add martinDTV/claude-fastapi-architect-skill
/plugin install fastapi-architect@fastapi-architect
### Manually
Copy the skill folder into your user or project skills directory:
bash
git clone https://github.com/martinDTV/claude-fastapi-architect-skill.git
# For every project (user scope)
cp -r claude-fastapi-architect-skill/plugins/fastapi-architect/skills/fastapi-architect ~/.claude/skills/
# Or only for one project (commit it so your team gets it too)
cp -r claude-fastapi-architect-skill/plugins/fastapi-architect/skills/fastapi-architect .claude/skills/
## Usage
The skill activates automatically when you work on a FastAPI project. Example prompts:
"Create a FastAPI backend for a clinic appointment system with patients, doctors and appointments."
"Add an invoicing module to this API."
"Our FastAPI app is getting big. Should we move to microservices?"
"Review this FastAPI project's structure and tell me what to fix first."
"Extract the notifications module into its own service."
## What's inside
.claude-plugin/marketplace.json # marketplace catalog
plugins/fastapi-architect/
├── .claude-plugin/plugin.json # plugin manifest
└── skills/fastapi-architect/
├── SKILL.md # decision workflow and non-negotiable rules
├── references/
│ ├── project-structure.md # layouts per stage, full example module
│ ├── architecture-decisions.md # stage guide, import-linter, microservice readiness, extraction playbook
> 🇲🇽 Español más abajo.
## Why another FastAPI skill
Most FastAPI skills either teach framework syntax or impose one architecture (usually full Clean Architecture with a DI container) on every project. Both fail in practice: a CRUD API wrapped in five layers is as costly as a 40-endpoint main.py.
This skill instead:
Right-sizes the architecture. Four stages, with explicit signals for moving between them. The default for production work is a modular monolith; ports and adapters are applied per module, only where the domain needs them.
Knows when a monolith should become microservices, and when it should not. It applies hard criteria (independent scaling, team ownership, release coupling, isolation, runtime needs) plus prerequisites, and pushes back when a split would produce a distributed monolith. When extraction is justified, it follows a strangler-fig playbook.
Enforces boundaries with tooling, not good intentions. import-linter contracts make cross-module imports and layer violations fail CI.
Ships verified code. Every snippet in the references passes ruff, mypy --strict and import-linter, and the example module's tests pass against PostgreSQL with current FastAPI, Starlette, SQLAlchemy 2.x and Pydantic v2, with warnings treated as errors.
Uses progressive disclosure. SKILL.md holds the decision workflow; detailed references load only when the task needs them.
## Install
### As a Claude Code plugin (recommended)
/plugin marketplace add martinDTV/claude-fastapi-architect-skill
/plugin install fastapi-architect@fastapi-architect
### Manually
Copy the skill folder into your user or project skills directory:
bash
git clone https://github.com/martinDTV/claude-fastapi-architect-skill.git
# For every project (user scope)
cp -r claude-fastapi-architect-skill/plugins/fastapi-architect/skills/fastapi-architect ~/.claude/skills/
# Or only for one project (commit it so your team gets it too)
cp -r claude-fastapi-architect-skill/plugins/fastapi-architect/skills/fastapi-architect .claude/skills/
## Usage
The skill activates automatically when you work on a FastAPI project. Example prompts:
"Create a FastAPI backend for a clinic appointment system with patients, doctors and appointments."
"Add an invoicing module to this API."
"Our FastAPI app is getting big. Should we move to microservices?"
"Review this FastAPI project's structure and tell me what to fix first."
"Extract the notifications module into its own service."
## What's inside
.claude-plugin/marketplace.json # marketplace catalog
plugins/fastapi-architect/
├── .claude-plugin/plugin.json # plugin manifest
└── skills/fastapi-architect/
├── SKILL.md # decision workflow and non-negotiable rules
├── references/
│ ├── project-structure.md # layouts per stage, full example module
│ ├── architecture-decisions.md # stage guide, import-linter, microservice readiness, extraction playbook
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/martindtv-claude-fastapi-architect-skill/)
- Source
- github · https://github.com/martinDTV/claude-fastapi-architect-skill
- Browse by field
- Open source
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.