Every time I started a new .NET project, I ended up repeating the same setup:
Clean Architecture folder structure
Layer separation (API → Application → Infrastructure → Domain) and Common layer
EF Core migrations
Generic services
CRUD patterns
Boilerplate configs and wiring
It usually took 1–2 days just to get everything into a clean, production-ready state before writing real features.
So I created my own reusable starter template to speed up development and reduce the “setup tax”.
It’s not a framework — just a clean, opinionated structure with examples, generic services, and documentation that explains how everything fits together.
Instead of keeping it private, I thought:
“Why not share it so other developers can benefit — and maybe improve it?”
👉 GitHub Repository:
https://github.com/safwancicem85/dotnet-clean-architecture-template
Please don’t hesitate to drop suggestions, issues, or ideas.
I really appreciate any recommendations the community can give.
Here’s an architecture visualization I’m experimenting with:
👉 Declaimer: the uploaded images are the structure of full template.
I’d love to hear suggestions or improvements from the .NET community!


Top comments (0)