Core and contracts provide the shared framework foundation. Extension dependency sets vary; see Compatibility for released package metadata and the configured boundaries.
| Package | Description |
|---|---|
quadkit | Application, DI container, providers, modules, YAML config, Result, logging |
quadkit-contracts | Shared protocols, types, and exceptions (typing-extensions dependency) |
The CLI pulls them in when you scaffold:
uv add quadkit-cliquadkit new project my-app --template apiNext Steps
Section titled “Next Steps”- Core Concepts — providers, DI, Result, modules
- Architecture — the boundary rule
- The Ecosystem — everything you add later