feature-slice-notification

To build end-to-end .NET notification features, you implement UseCases with Command/Query, Handler, and Validator patterns alongside Minimal API endpoints, permission-based authorization, and contract documentation across Application and Api layers.

The standard UseCase pattern for .NET Minimal API endpoints separates operations into Command or Query objects, processes them with a Handler, validates inputs with a Validator, and enforces directory structure and file naming across Application and Api layers.

Yes, you can refactor existing C# notification endpoints by applying structural and contract requirements, enforcing directory structure, file naming, and validation across Application and Api layers to maintain consistency during Create, Update, or Delete operations.

Set up permission-based authorization for .NET notification features by enforcing structural and contract requirements within the automated end-to-end feature development flow, ensuring the Api layer correctly validates permissions across endpoints.

Yes, you need ripgrep installed as a dependency to automate the generation of .NET UseCase handlers, validators, and Minimal API endpoints, as the scripts rely on it to enforce directory structure and file naming.