What problem does it solve?
Contract-first, architecture-first guidelines provide a structured approach to designing backend systems with a single source of truth (schemas) and clearly separated layers (domain, application, infrastructure).
This approach helps prevent drift between contracts and implementation, reduces cognitive load when wiring services, and enables scalable governance across teams.
Core Features & Use Cases
- Self-contained slices per business capability with domain, application, and infrastructure layers wired through a single composition root.
- Contracts as the SSOT driving generation, validation, and drift protection, plus ADRs to document architectural choices.
- Ports and adapters enforce dependency inwardness, enabling test doubles and flexible deployment of production vs. test environments.
- Criteria-based patterns and test strategies (object mothers, doubles) to support fast, deterministic testing across layers.
Quick Start
Clone the repository and follow Steps 1 through 8 to bootstrap a contract-first, screaming-slices project.