Skip to content
Clean Minimal API
Lean Mean Clean Apps

Five templates, one brand, one search box. Everything in the docs is in here, including the bits we hoped you'd skim.

Try one of these

Results say which template they came from, so you won't end up reading about Lambda when you wanted GraphQL. Again.

A Lean Mean Clean Apps template for .NET 10

Clean Architecture for Minimal APIs, minus the ceremony.

A .NET 10 template that gives you a tested, layered HTTP API in two commands. Fewer layers than an onion, more than a sandwich.

dotnet new install CleanMinimalApi.Template
dotnet new cleanminimalapi --name WorksOnMyMachine.Movies
cd WorksOnMyMachine.Movies && docker compose up -d

Three layers, the tests, a Dockerfile and a CI pipeline. Go and tell your team you've been working on it all week.

Endpoints, not boilerplate

Minimal API endpoints grouped by feature. Each one sends a command or query through Mediator and gets out of the way.

Docs that write themselves

OpenAPI comes from the XML comments you were going to write anyway, and Scalar turns it into an API reference you can actually click around in.

Errors with manners

Validation lives in the Application layer with FluentValidation, and every failure comes back as Problem Details (RFC 9457). No mystery 500s.

Tested like it matters

xUnit, Shouldly and a 95% coverage gate. Every test gets its own throwaway SQLite database, so nobody steps on anybody’s toes.

Clean Minimal API is one of five Lean Mean Clean Apps templates. They share the same Application and Infrastructure layers, the same tests and the same pipeline. Only Presentation changes. Like a family, really. Same genes, different haircuts.

Each template gets the same ring logo in its own colour. The rings follow the Clean Architecture diagram, from the entities in the core out to the frameworks and drivers on the edge. Minimal APIs drew emerald, which suits something that keeps everything lean and green. The logos, colours and everything else live in the brand kit.