swashbuckle-dotnet

What problem does it solve?

Manually configuring Swagger/OpenAPI for Jarvis .NET backends with multi-version support, standardized BaseResponse schemas, and security schemes (JWT, API Key) is time-consuming and prone to misconfiguration, especially when adhering to Jarvis' clean architecture and layer extension patterns.

Core Features & Use Cases

• End-to-end Swagger orchestration: Automates setup of Jarvis.Swashbuckle for multi-version Swagger UI with standardized BaseResponse schema support, aligned with Jarvis' clean architecture layer patterns.
• Modular workflow support: Provides step-by-step workflows for initial Swagger integration into new Jarvis Host projects and for adding new API versions or security schemes to existing setups.
• Atomic security providers: Includes dedicated sub-skills for configuring JWT Bearer and API Key security schemes in Swagger, with links to corresponding Jarvis authentication configurations.
• Use Case: A developer building a Jarvis .NET 9 e-commerce API can use this skill to enable Swagger with v1 and v2 support, add JWT authentication to the Swagger UI authorize button, and ensure all API responses use the standard BaseResponse schema, all in minutes instead of hours of manual configuration.

Quick Start

Use the swashbuckle-dotnet skill to configure multi-version Swagger with JWT security for your existing Jarvis .NET Host project.