Umbrella
Official@umbrella-libraries
Offers standardized scaffolding and migration patterns for .NET enterprise applications, focusing on EF Core, Blazor, and ASP.NET Core architecture.
Agent Skills by Umbrella
Showing 21 vetted skills indexed across 1 GitHub repositories.
umbrella-librariesblazor-scaffold-index-page
Generate a paginated, sortable Blazor index page with UmbrellaGrid.
umbrella-librariesdotnet-scaffold-ef-repository
Scaffold repository interface, implementation, IncludeMap, and DI registration for EF Core entities.
umbrella-librariesdotnet-scaffold-file-authorization-handler
Scaffold a .NET file authorization handler for directory-based access control.
umbrella-librariesdotnet-rename-client-repository-to-service
Rename client Repository to Service and migrate files, namespaces, DI registrations, and Blazor references.
umbrella-librariesblazor-scaffold-manage-page
Scaffold Blazor manage pages for create/edit CRUD operations.
umbrella-librariesdotnet-scaffold-auth-policy
Define and register named authorization policies in shared project files.
umbrella-librariesdotnet-migrate-automapper-to-mapperly
Migrate AutoMapper Profile mappings to Mapperly mappers with DI rewiring.
umbrella-librariesdotnet-scaffold-architecture-tests
Generate a .NET architecture test scaffold enforcing layer dependencies and visibility.
umbrella-librariesdotnet-scaffold-api-server-models
Generate API model records implementing Umbrella shared interfaces for Web.Shared.Models.Api.
umbrella-librariesdotnet-migrate-repo-controller-to-data-service
Migrate a GenericRepositoryApiController to a Pattern 2 controller service for Blazor SSR.
umbrella-librariesdotnet-scaffold-service
Scaffold Umbrella Core.Logic service skeletons with interfaces, models, and DI registration.
umbrella-librariesblazor-register-nav-item
Add a navigation item to Blazor NavMenu.razor within an AuthorizeView policy.
umbrella-librariesdotnet-scaffold-api-repo-controller
Scaffold ASP.NET Core API controllers delegating CRUD operations to repositories via GenericRepositoryApiController.
umbrella-librariesdotnet-scaffold-client-data
Scaffold a client HTTP data service implementing IManage<Name>Service with GenericHttpDataService.
umbrella-librariesdotnet-scaffold-resource-auth-handler
Scaffold an ASP.NET Core IAuthorizationHandler for row-level access control.
umbrella-librariesdotnet-scaffold-ef-entity
Builds an EF Core entity class and registers it in the DbContext using Umbrella conventions.
umbrella-librariesdotnet-scaffold-mapperly-factories
Generate Mapperly mappers for EF Core entities and API/client models.
umbrella-librariesdotnet-scaffold-file-handler
Generate file handler interface, implementation, DirectoryNames constant, and DI registration.
umbrella-librariesnuget-safe-upgrade
Upgrade NuGet packages across multi-targeted .NET projects with exclusions and build verification.
umbrella-librariesdotnet-scaffold-api-data-service-controller
Scaffold an API controller with UmbrellaRepositoryDataService and DI registration.
umbrella-librariesdotnet-add-ef-migration
Automates EF Core migration generation by auto-detecting the relevant .NET project and DbContext.
Frequently Asked Questions About Umbrella
FAQPage SchemaWhat specific development tasks does Umbrella support?▼
Umbrella enables rapid scaffolding of EF Core entities, Blazor CRUD pages, and ASP.NET Core controllers. It supports architectural enforcement, Mapperly migration, and standardized dependency injection registration for enterprise-grade .NET applications.
Which developers benefit most from these capabilities?▼
Backend and full-stack engineers working within the .NET ecosystem benefit from these standardized patterns. It is specifically designed for teams maintaining complex enterprise solutions requiring consistent architecture, security policy implementation, and efficient data layer management.
What are the prerequisites for using these scaffolding features?▼
Users must have a .NET project structure that adheres to Umbrella conventions, specifically utilizing EF Core for data persistence and Blazor for UI components. The environment requires a standard .NET development setup with access to the project's solution and configuration files.