clean-architecture-scaffolder

Clean / Vertical Slice Architecture Scaffolder

Generate a consistent, opinionated .NET solution structure — either Clean Architecture (layered) or Vertical Slice Architecture (feature-first) — with project references wired correctly and one working sample feature so the pattern is obvious.

Input — point it at your project

For a new solution, just take the name. For an existing project, point this at the repo so it matches the house style instead of imposing one:

• A project or repo root — detect the current architecture and conventions, then scaffold a new slice/feature that fits.
• A GitHub URL — clone first, then inspect: git clone --depth 1 <url> /tmp/repo && cd /tmp/repo

Detect the existing style yourself before generating, e.g.:

find <target> -name "*.sln" -o -name "*.csproj" | grep -vi "/obj/\|/bin/"
ls <target>/**/Features 2>/dev/null   # Vertical Slice?  vs  Domain/Application/Infrastructure folders = Clean
grep -rln "ICarterModule\|IRequestHandler\|MediatR\|FluentValidation\|OneOf" --include=*.cs <target> | head

When adding to an existing codebase, read one existing feature first and mirror its conventions (endpoint style, validation, result type) so the new code looks like it belongs.

When this runs

The user is starting a new .NET solution, restructuring one, or adding a feature to an existing one. For new work, decide the style first (ask if unclear). For existing projects, detect the style from the code and match it:

• Clean Architecture — layered (Domain / Application / Infrastructure / API). Good for larger teams, strong boundaries, swappable infrastructure.
• Vertical Slice Architecture — organized by feature, each slice self-contained. Good for fast-moving teams, less ceremony, fewer cross-layer jumps.

Also confirm: project name, .NET version (default 8/9), and whether they want CQRS/MediatR (default yes for both styles).

Output: shell commands + key files

Produce (a) the dotnet CLI commands to create projects and references, and (b) the contents of the key files. The user should be able to run the commands and paste the files and have a building solution.