Structure .NET APIs into self-contained vertical slices with endpoints and handlers.
npx skills add https://github.com/Resgrid/Core --skill vertical-slice-resgrid
Please help me install this Agent Skill. Skill: vertical-slice Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/vertical-slice Command: npx skills add https://github.com/Resgrid/Core --skill vertical-slice-resgrid
Vertical Slice Architecture (VSA) eliminates the friction of scattering a single feature across controllers, services, and repositories by keeping each feature self-contained around its endpoint and handler.
Features/Orders/CreateOrder.cs) to reduce navigation and cognitive load.Common/ or Shared/ rather than creating tangled dependencies.Load this skill when designing or refactoring a .NET API so that each feature folder contains the endpoint and handler for one operation, with validation and request/response types colocated.
High-intent search queries and answers about installing and using this skill.
Vertical slice architecture structures a .NET API by co-locating endpoint wiring, request/response types, validation, and handler logic inside a single feature folder like Features/Orders/CreateOrder.cs to reduce navigation and cognitive load.
Organizing feature folders in ASP.NET Core involves grouping each business capability as a self-contained vertical slice with its endpoint, handler, and validation colocated, preventing direct feature-to-feature calls and reducing layered abstractions.
Yes, vertical slice architecture supports Wolverine convention-based handlers, Mediator-style source-generated handlers, or raw handler classes, treating the handler as the unit of work to discourage god-classes and large multi-purpose service layers.
Prevent tight coupling between vertical slices by disallowing direct feature-to-feature calls and routing shared behavior or contracts to a Common or Shared folder boundary, keeping each slice self-contained.
Refactor a layered .NET API into vertical slices when scattering a single feature across controllers, services, and repositories creates friction, and you need cohesive feature-first folder structures with minimized cross-feature coupling.
Vertical slices scale for larger .NET applications by adding module boundaries around cohesive features and using shared contracts only when necessary, providing practical growth paths while maintaining handler-as-unit-of-work conventions.
TrossitecReorganize .NET codebases into feature folders with isolated handlers and endpoints.
codewithmukeshOrganize code by feature into vertical slices with endpoints, handlers, and validation.
shahdanishOrganize .NET API endpoints and handlers into feature folders.
korallisArchitect scalable backend services using layered architecture and dependency injection.