Generate OpenAPI 3.1 documentation for .NET 10 APIs using Microsoft.AspNetCore.OpenApi.
npx skills add https://github.com/shahdanish/vibepos --skill openapi-shahdanish
Please help me install this Agent Skill. Skill: openapi Source: https://github.com/shahdanish/vibepos/tree/main/skills/openapi Command: npx skills add https://github.com/shahdanish/vibepos --skill openapi-shahdanish
It solves the problem of producing accurate, maintainable OpenAPI specifications for .NET web APIs without relying on third-party tooling that may be outdated or redundant.
Use the openapi skill to generate and serve an OpenAPI document by calling AddOpenApi in your .NET app and mapping MapOpenApi in development.
High-intent search queries and answers about installing and using this skill.
To generate OpenAPI documentation without Swashbuckle, use the built-in Microsoft.AspNetCore.OpenApi pipeline by calling AddOpenApi and MapOpenApi in your .NET 10 application. This framework-maintained approach replaces outdated third-party tooling.
To ensure correct response schemas in your .NET OpenAPI document, use TypedResults for your endpoint responses. TypedResults reliably infers response schemas automatically, allowing the built-in Microsoft.AspNetCore.OpenApi pipeline to generate accurate specifications.
To add security schemes to OpenAPI documents in .NET, apply document or operation transformers like IOpenApiDocumentTransformer. This transformer-based customization allows you to document security schemes such as Bearer JWT authentication directly within the generated specification.
Yes, you can serve multiple OpenAPI documents from a single .NET application using the built-in Microsoft.AspNetCore.OpenApi pipeline. The framework supports multiple OpenAPI documents selection, allowing you to map different specifications for various API segments.
Endpoint metadata enrichment improves .NET OpenAPI generation by setting WithName, WithSummary, WithDescription, and WithTags on endpoints. This provides strong operation identifiers for the generated spec, resulting in more accurate client generation and API discovery.
A limitation of the built-in .NET OpenAPI pipeline is that it requires .NET 10 and relies heavily on TypedResults for accurate response schema inference. Without TypedResults, schema generation may lack the reliability needed for correct documentation.
ResgridGenerate OpenAPI 3.1 documentation for .NET 10 endpoints using built-in Microsoft OpenAPI and transformers.
Maj3D10Generate OpenAPI 3.1 documentation for .NET 10 APIs using Microsoft.AspNetCore.OpenApi.
TrossitecGenerate OpenAPI documentation for .NET 10 APIs using transformers and TypedResults.
The13thNodeDesigns REST and GraphQL API contracts with OpenAPI 3.0 specifications.
