build-feature

Implementing a vertical-slice feature in a Blazor WebAssembly .NET repository requires a step-by-step Red-Green-Refactor workflow that scaffolds domain entities, application commands, persistence repositories, controllers, and presentation components.

The Red-Green-Refactor workflow for .NET feature development enforces test-first implementation by writing failing tests, running the test executable, adding minimal production code, and proving success through explicit build, format, and code analysis checks before proceeding.

Yes, this workflow supports DbUp database migrations for Blazor applications by scaffolding multi-layer patterns across persistence, contracts, API controllers, and presentation components within the approved vertical-slice feature plan.

You enforce test-first development and code analysis in a .NET Blazor project by applying safety gates that require explicit dotnet build, format, code-analysis proofs, running the test executable, and human approval before marking any plan step complete.

Yes, you can use this approach to add CRUD operations across all .NET layers, as it produces patterns and templates for domain, application, persistence, contracts, API controllers, DbUp migrations, and presentation components using a reference feature.

You need a human approval gate during dotnet feature implementation after running tests and code analysis proofs, ensuring explicit user approval is required before marking any step in the vertical-slice feature plan done.