minimal-api

What problem does it solve?

Minimal APIs in .NET 10 can become inconsistent, untyped, and scattered across Program.cs, which leads to poor OpenAPI documentation, brittle validation, and hard-to-maintain routing. This Skill prescribes a composable, architecture-friendly approach that keeps endpoint wiring isolated, ensures compile-time response types, and centralizes cross-cutting concerns so teams can scale HTTP surface areas without degrading quality.

Core Features & Use Cases

• Endpoint Group Auto-Discovery: Define one IEndpointGroup per feature and use a single MapEndpoints call so Program.cs never grows with each new feature.
• Type-Safe Responses: Use TypedResults and explicit union return types to produce accurate OpenAPI schemas and avoid untyped IResult leaks.
• Parameter Binding & Validation: Recommend [AsParameters] for complex queries, header binding conventions, and endpoint filters (e.g., FluentValidation) for request validation.
• OpenAPI, Rate Limiting & Caching: Use built-in AddOpenApi, AddRateLimiter, and AddOutputCache patterns to generate docs, protect APIs, and cache responses.
• Cross-cutting Filters: Apply endpoint filters at group or endpoint level for logging, validation, and auth policies.

Quick Start

Scaffold an IEndpointGroup that registers /api/orders endpoints using TypedResults, endpoint filters for validation, and OpenAPI metadata.