What problem does it solve? ASP.NET Core services need an accurate, machine-readable OpenAPI document and a browsable docs UI, but hand-written specs drift from the running code and misconfigured generators produce thin, incomplete contracts. ## Core Features & Use Cases - Generator Selection by Framework Floor: Picks Swashbuckle or NSwag on .NET 8 and the built-in Microsoft.AspNetCore.OpenApi with AddOpenApi / MapOpenApi on .NET 9 and up. - Spec Shaping and Security Schemes: Uses document, operation, and schema transformers to declare bearer/JWT security schemes, split versioned documents, and keep schemas accurate via TypedResults and Produces metadata. - Docs UI and Client Generation: Serves a gated Scalar UI and emits the document at build time so consumers generate TypeScript types or typed clients with NSwag, Kiota, or openapi-typescript. - Use Case: When adding API documentation to a new .NET 9 minimal API, use this Skill to wire AddOpenApi with a bearer security transformer, gate the Scalar UI to development, and verify the generated spec lists every expected path. ## Quick Start Use the dotnet-openapi skill to add a generated OpenAPI document with a Bearer security scheme and a development-only Scalar UI to my ASP.NET Core service.