neo-dotnet-minimal-apis

# .NET Minimal APIs Expert Skill ## Trigger On - The user requests to create, debug, refactor, or review .NET Minimal APIs. - The project's `Program.cs` contains `WebApplication.CreateBuilder(args)` and is not configured with a Controllers directory. - The target framework is .NET 6.0 (LTS) and above. - There is a need to optimize API performance or simplify Web API architecture. ## Workflow 1. **Perceive (Architecture Awareness):** - Check `.csproj` to identify `TargetFramework`. - Analyze `Program.cs` to distinguish whether it uses simple endpoints or adopts a Module-based or Vertical Slice organization. - Identify whether OpenAPI (Swagger) support has been configured. 2. **Reason (Planning Phase):** - Evaluate whether "Route Groups" need to be introduced to optimize organizational structure. - Determine whether to use "Endpoint Filters" to handle cross-cutting concerns (such as parameter validation). - Choose the most appropriate syntax based on the .NET version (e.g., `TypedResults` in .NET 7+). 3. **Act (Execution Phase):** - Write clean, high-performance Minimal API code, prioritizing Lambdas or extension methods. - Implement strong typing and DTOs (prioritize using `record`). - Integrate dependency injection, avoiding the Service Locator pattern. 4. **Validate (Standard Validation):** - Validate whether the endpoints correctly return expected HTTP status codes. - Check whether the generated OpenAPI documentation is complete. - Ensu...