What problem does it solve?
It solves the problem of writing ASP.NET Core Web API endpoints that consistently return the right HTTP status codes, generate accurate OpenAPI/Swagger documentation, and handle errors safely and uniformly.
Core Features & Use Cases
- Endpoint design with correct HTTP semantics: Choose controller vs minimal API patterns, apply consistent status codes, and ensure POST creates use 201 Created with a Location header.
- API-ready DTOs with OpenAPI quality: Use sealed record request/response types, enforce immutability, add XML doc summaries for richer OpenAPI output, and use DateTimeOffset for date/time fields.
- Global error handling and request validation: Add centralized exception-to-ProblemDetails mapping and ensure minimal APIs have explicit validation wiring where applicable.
- Developer ergonomics: Provide conventions for TypedResults, enum string serialization, CancellationToken propagation, and add a root-level .http test file for manual verification.
Quick Start
Ask the AI: “Create a new ASP.NET Core Web API endpoint that follows existing controller/minimal API conventions, uses sealed DTOs with XML summaries, returns correct status codes with ProblemDetails on errors, and updates OpenAPI plus a matching .http test request.”