dotnet-scaffold-api-data-service-controller

This Skill scaffolds a thin .NET API controller backed by a controller service that implements UmbrellaRepositoryDataService, separating transport-layer logic from business logic for predictable dependency injection and repository reuse.

The repository data service pattern supports Blazor SSR pre-rendering by providing a clean extension point for lifecycle hooks when the client project interface exists, enabling shared repository logic across server and client boundaries.

Yes, you can use this scaffold to standardize dependency injection wiring for API controllers. It enforces explicit lifecycle hooks, standardizes constructor dependencies, and ensures proper interface placement within your .NET API projects.

The best way to separate concerns in a .NET API controller is to use a controller service wrapper around repository logic. This scaffold generates a transport-layer wrapper that isolates API endpoints and enables reuse across server and client boundaries.

Your scaffolded API controller needs a concrete controller service to implement the UmbrellaRepositoryDataService pattern, which ensures repository logic is reusable across server and client boundaries while maintaining explicit lifecycle hooks and standardized model types.