backend-develop

To generate ASP.NET Core backend code from feature specs, provide a specification like SPEC-001 to automate the creation of Domain entities, Application use cases, Infrastructure repositories, and API controllers following Clean Architecture and DDD principles.

Automated backend code generation handles Domain-Driven Design patterns by processing feature specs to create distinct Domain, Application, Infrastructure, and API layers. It enforces Vertical Slices patterns and utilizes the Result Pattern for consistent error handling across the generated C# files and EF configurations.

Yes, you can use this to implement clean architecture vertical slices in .NET applications. It specifically automates the generation of backend code for .NET applications by adhering to Clean Architecture, Domain-Driven Design, and Vertical Slices patterns based on your provided feature specs.

The best way to scaffold EF Core configurations and use cases for a new feature is to provide a feature spec to this Skill. It automatically generates the necessary EF configurations, handlers, validators, requests, and responses alongside the API controllers and domain entities.

Yes, you need specific folder structures for backend code generation in ASP.NET Core. The Skill explicitly requires adherence to specific folder structures, naming conventions, and the Result Pattern for error handling to successfully generate the Domain, Application, and Infrastructure layers.

Clean architecture code generation requires the Result Pattern for error handling to ensure consistent validation and error reporting across the generated Application use cases. This enforces project-specific conventions, reducing manual coding errors while maintaining strict Domain-Driven Design boundaries.