Start with one of the walkthroughs below. Each is complete for what it covers: a problem, a compiling example, and a link into the package that owns the detail. Anything deeper lives with its package — every package page has a Quickstart / Guide / How-tos strip.
If you have not scaffolded yet:
uv add "quadkit-cli>=0.0.42,<0.1"quadkit new project my-app --template web-apicd my-appquadkit runComing from FastAPI? Keep Starlette routing and Pydantic; add a composition root. The map is Migrating from FastAPI.
Walkthroughs
Section titled “Walkthroughs”| Guide | When to read it |
|---|---|
| The quadkit CLI | new, gen, run, dev, db, config |
| Testing | Test harnesses, fakes, and compliance suites |
| Real-time web | SSE, WebSocket, and streaming responses |
| Deployment | quadkit run in production |
| Observability | Logs, health probes, tracing, and an incident runbook |
| Contracts & boundaries | Where a shared type, protocol, or exception belongs |
| Migrating from FastAPI | Keep your Starlette instincts, add a composition root |
How-tos
Section titled “How-tos”How-tos are owned by the matching package GUIDE, so they ship with the code that implements them:
quadkit— application lifecycle, providers, and the containerquadkit-web— routing, middleware, and request handlingquadkit-cli— scaffolding, generators, and project operationsquadkit-testing— fixtures and test harnessesquadkit-contracts— protocols, value objects, and exceptions
Next Steps
Section titled “Next Steps”- Your First App — the 60-second walkthrough
- Project Structure — where generated files land
- The Ecosystem — the published packages, grouped by purpose