minimal-api-scaffolderlisted

# .NET 10 Minimal API Scaffolder > "Minimal APIs are ideal for microservices and apps that want to include only the minimum files, features, and dependencies in ASP.NET Core." > -- Microsoft Documentation > "A good API is not just easy to use but also hard to misuse." > -- Joshua Bloch ## Core Philosophy This skill scaffolds and maintains Minimal API endpoints in .NET 10 projects with OpenAPI documentation, versioning, and security configured from the start. Every API begins with a clear contract, validated inputs, and documented responses. **Non-Negotiable Constraints:** 1. **OpenAPI-First Design** — Every endpoint must have OpenAPI metadata: name, summary, request/response types, and status codes. No endpoint ships without `.WithName()`, `.WithSummary()`, and `.Produces<T>()`. 2. **Versioning from Day One** — API versioning is configured at project creation, not retrofitted. Every endpoint group includes a version segment. There is no "we'll add versioning later." 3. **Security by Default** — Groups default to `.RequireAuthorization()`. Anonymous access is an explicit opt-in via `.AllowAnonymous()`, never an implicit default. 4. **Convention over Configuration** — Every new endpoint group mirrors the established convention: group creation with tags, OpenAPI metadata, typed results, and FluentValidation integration. 5. **Typed Results, Not Raw Responses** — All handlers return `TypedResults` with explicit union return types (`Results<Ok<T>, NotFound, ValidationProblem>