⚡ BlitzSliceForge

Fast .NET scaffolder for Blazor + CQRS + Vertical Slice Architecture solutions

BlitzSliceForge (bsf) is a CLI tool that scaffolds a fully structured .NET 9 solution following Clean Architecture and Vertical Slice principles in seconds. Stop wasting time creating projects, linking references, and setting up folder structures manually — let bsf do the heavy lifting.

---

✨ Features

• 🚀 One-command scaffolding — generates an entire solution structure instantly
• 🏗️ Clean Architecture — Domain, Application, Infrastructure, and Web layers out of the box
• 🌐 Blazor Interactive — pre-configured Blazor project with Auto interactivity mode
• 🧪 Test projects included — test projects created and linked for every layer
• 📁 Opinionated folder layout — src/, tests/, docs/adr/, docker/, .github/workflows/
• 📄 Common files — .gitignore, global.json, Directory.Build.props, and README.md auto-generated
• ⚙️ Framework selection — choose target .NET version (e.g., net8.0, net9.0) with a simple parameter
• 🔍 SDK validation — verifies the required .NET SDK is installed before scaffolding
• 📦 Distributed as a .NET tool — install globally and use anywhere

---

📦 Installation

Prerequisites

• .NET 9 SDK or later

Install globally

dotnet tool install --global BlitzSliceForge.Cli

Check installation

bsf --help

Descripción:
  bsf - Blitz Slice Forge

Uso:
  BlitzSliceForge.Cli [opciones]

Opciones:
  -n, --name <n> (REQUERIDO)    Name of the solution
  -f, --framework <net8|net9>  Target .NET framework version (e.g. net8)
  -o, --output <o>            Output path (default: solution name)
  -?, -h, --help                   Mostrar ayuda e información de uso
  --version                        Mostrar información de la versión

Uninstall

dotnet tool uninstall BlitzSliceForge.Cli --tool-path .tools 

---

🚀 Quick Usage

Generate a new solution

bsf --name MyAwesomeApp

This creates a solution named MyAwesomeApp in a folder with the same name in the current directory.

Generate a solution with a specific .NET framework

bsf --name MyAwesomeApp --framework net8

Specify a custom output directory

bsf --name MyAwesomeApp --output C:/Projects/MyAwesomeApp

CLI Options

Option	Alias	Description	Required
--name	-n	Name of the solution	✅ Yes
--framework	-f	Target .NET framework version (e.g. net8)	❌ No
--output	-o	Output path (defaults to solution name)	❌ No

---

🏗️ Generated Structure

When you run bsf --name MyAwesomeApp, the following structure is generated:

MyAwesomeApp/
├── .github/
│   └── workflows/           # CI/CD workflow templates
├── docker/                  # Docker configuration
├── docs/
│   └── adr/                 # Architecture Decision Records
├── src/
│   ├── MyAwesomeApp.Domain/             # Entities, Value Objects, Interfaces
│   ├── MyAwesomeApp.Application/        # Use Cases, CQRS Handlers, DTOs
│   ├── MyAwesomeApp.Infrastructure/     # EF Core, External Services, Repos
│   └── MyAwesomeApp.Web/               # Blazor Server/WASM (Auto mode)
├── tests/
│   ├── MyAwesomeApp.Domain/             # Domain unit tests
│   ├── MyAwesomeApp.Application/        # Application unit tests
│   └── MyAwesomeApp.Infrastructure/     # Infrastructure unit tests
├── .gitignore
├── Directory.Build.props
├── global.json
├── README.md
└── MyAwesomeApp.sln

Project References

The generated projects are automatically linked following Clean Architecture dependency rules:

graph TD
    A["🌐 MyAwesomeApp.Web<br/><i>Blazor - Presentation</i>"] --> B
    B["⚙️ MyAwesomeApp.Application<br/><i>Use Cases / CQRS</i>"] --> C
    B --> D
    D["🔌 MyAwesomeApp.Infrastructure<br/><i>Data Access / External</i>"] --> C
    C["🧱 MyAwesomeApp.Domain<br/><i>Entities / Core Logic</i>"]

    style A fill:#6C3FC5,stroke:#4A2A8A,color:#fff
    style B fill:#0078D4,stroke:#005A9E,color:#fff
    style C fill:#107C10,stroke:#0B5E0B,color:#fff
    style D fill:#D83B01,stroke:#A52C00,color:#fff

Loading

Application → references Domain + Infrastructure Infrastructure → references Domain

---

📊 Project Status

timeline
    title BlitzSliceForge Roadmap
    section MVP ✅
        v0.0.1 : Solution scaffolding
               : Clean Architecture layers
               : Blazor Web project (Auto)
               : Test projects per layer
               : Project reference linking
               : Common file templates
               : SDK version validation
    section Next Steps 🔮
        Backlog : Entity scaffolding per feature
                : CQRS handler generation
                : Vertical Slice feature scaffolding
                : MediatR integration templates
                : Docker Compose templates
                : GitHub Actions CI/CD templates
                : NuGet package publishing

Loading

Current Status: MVP ✅

Feature	Status
Solution generation	✅ Done
Clean Architecture project layout	✅ Done
Blazor Web project (Auto interactivity)	✅ Done
Test projects for each layer	✅ Done
Automatic project reference linking	✅ Done
Common templates (.gitignore, global.json, etc.)	✅ Done
.NET SDK validation	✅ Done
Global .NET tool distribution	✅ Done
Framework selection	✅ Done
Unit tests for CLI core logic	✅ Done

Next Steps 🔮

Feature	Status
Entity scaffolding per feature/slice	📋 Planned
CQRS command/query handler generation	📋 Planned
Vertical Slice feature folder scaffolding	📋 Planned
MediatR integration templates	📋 Planned
Docker Compose templates	📋 Planned
GitHub Actions CI/CD pipelines	📋 Planned

---

🛠️ Building from Source

# Clone the repository
git clone https://github.com/AlejBlasco/BlitzSliceForge.git
cd BlitzSliceForge

# Build the project
dotnet build

# Run locally
dotnet run --project src/BlitzSliceForge.Cli -- --name TestSolution

# Pack as a .NET tool
dotnet pack src/BlitzSliceForge.Cli -c Release

# Install locally from the generated .nupkg
dotnet tool install --global --add-source ./src/BlitzSliceForge.Cli/nupkg BlitzSliceForge.Cli

---

🧪 Running Tests

dotnet test

The test suite covers the core logic of BlitzSliceForge.Cli using xUnit, Moq and FluentAssertions.

Test coverage

Area	Test class	What is verified
Enums	AvailableFrameworksEnumExtensionsTests	TFM string mapping, out-of-range exception
Models	GenerationOptionsTests	Default values, property assignment
Models	ProjectGenerationOptionsTests	ProjectName, ProjectDirectory, FullProjectPath computed properties
Services	DotNetCliResponseTests	Constructor, GetOutputLines with empty / Unix / Windows / mixed line endings
Services	SdkCheckerServiceTests	Null guard, SDK found → true, not found → false, CLI called once
Services	TemplateRendererServiceTests	Missing template, static render, model interpolation, cancellation
Generators	ProjectTemplateTests	Project count, src/tests layout, framework propagation, Blazor options
Generators	ProjectGeneratorTests	Null guard, CLI invocation count, directory creation, reference linking

Run with coverage

dotnet test --collect:"XPlat Code Coverage"

---

📄 License

This project is licensed under the MIT License — see the LICENSE file for details.

---

🤝 Contributing

Contributions are welcome! Feel free to open an issue or submit a pull request.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

---

Architectural Decisions

All important decisions are documented in docs/adr/

• ADR 001: Support for Multiple .NET Framework Versions