Free .NET templates
Start with the architecture already in place
Production-ready .NET 10 solution templates you can clone, rename, and build on. Pick the shape that fits your team and the whole repository lands in your inbox.
Choose layers, organize by feature, or add Aspire orchestration. The Claude Code skills come with the Clean Architecture template.
Downloaded by 45,000+ developers
Layered .NET solution
Clean Architecture
I want clear boundaries between my application layers.
Domain, Application, Infrastructure, and Web.Api projects with the dependency rule enforced by architecture tests, so a wrong reference fails the build.
- CQRS
- JWT + refresh tokens
- EF Core
- HybridCache
- OpenTelemetry
- Testcontainers
5 projects · 45,000+ developers
Get the free templateOne file per feature
Vertical Slice Architecture
I want to keep each feature in one place.
A single project where each use case lives in one file. The command, validator, handler, and endpoint sit together instead of scattering across four projects.
- Lightweight CQRS
- Scrutor
- FluentValidation
- Minimal APIs
- HybridCache
- Testcontainers
1 project · Copy a file to add a feature
Get the free templateCloud-native orchestration
Aspire Clean Architecture
I want Aspire to run my API and its dependencies together.
The same layered solution wired up with .NET Aspire. The AppHost starts PostgreSQL, the API, and the dashboard together, in the right order.
- AppHost
- ServiceDefaults
- OpenTelemetry
- Health checks
- Service discovery
One command boots everything
Get the free Aspire templateClaude Code skill pack
Claude Code Skills
I want Claude Code to follow my architecture conventions.
Seven skills that teach Claude Code the conventions of the Clean Architecture template. Describe a feature in plain English and it builds the whole slice, tests included.
- /add-feature
- /add-entity
- /add-tests
- /ca-review
Includes the Clean Architecture template
Get the free template + skillsTwo modules, one app
Modular Monolith Architecture
I want separate business modules in one deployment.
Create an event, publish it, and reserve seats in a .NET 10 app. Events and Ticketing own separate schemas and exchange a versioned event through a local outbox worker.
- .NET 10
- Vertical slices
- EF Core
- PostgreSQL
- Outbox + inbox
- Testcontainers
2 modules · 1 PostgreSQL database
Get the free modular monolith templateTwo services, separate data
Microservices
I want to see how services exchange messages and recover from failure.
Place an order and follow its event into a second .NET 10 service. Separate PostgreSQL databases, RabbitMQ, outbox and inbox code, plus scripts that test failure and recovery.
- .NET 10
- RabbitMQ
- PostgreSQL
- Outbox + inbox
- Request retries
- Docker Compose
2 APIs · 2 databases · 1 message broker
Get the free microservices templateWhat you actually get
A real solution, not a folder of empty projects
Each template is the setup I would start a new project with today, with the decisions that usually eat the first week already made.
Free forever, updates included
Every template is free, and so is every future version. You get an email when a new one ships.
Running in two commands
docker compose up starts the dependencies, dotnet run starts the API. No setup checklist to work through first.
Targets .NET 10
Directory.Build.props carries notes for retargeting to .NET 8 or .NET 9 if you are not on the latest runtime yet.
Tested, not just scaffolded
Unit, integration, and architecture tests come with the solution, running against real dependencies through Testcontainers.
Want the reasoning behind them?
The templates show you the what. My courses walk through the why, decision by decision, building the same architectures from an empty solution.
Explore the courses