Get the FREE Ultimate OpenClaw Setup Guide →

ln-775-api-docs-generator

npx machina-cli add skill levnikolaevich/claude-code-skills/ln-775-api-docs-generator --openclaw
Files (1)
SKILL.md
6.7 KB

ln-775-api-docs-generator

Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-770-crosscutting-setup

Configures API documentation with Swagger/OpenAPI.


Overview

AspectDetails
InputContext Store from ln-770
OutputSwagger/OpenAPI configuration
Stacks.NET (Swashbuckle), Python (FastAPI built-in)

Phase 1: Receive Context + Analyze API Structure

Accept Context Store and scan for API endpoints.

Required Context:

  • STACK: .NET or Python
  • PROJECT_ROOT: Project directory path

Idempotency Check:

  • .NET: Grep for AddSwaggerGen or UseSwagger
  • Python: FastAPI has built-in OpenAPI, check for custom configuration
  • If found: Return { "status": "skipped" }

API Analysis:

  1. Scan for controller/router files
  2. Identify authentication method (JWT, OAuth2, API Key)
  3. Check for API versioning

Phase 2: Research Documentation Standards

Use MCP tools for current documentation.

For .NET:

MCP ref: "Swashbuckle ASP.NET Core OpenAPI Swagger configuration"
Context7: /domaindrivendev/Swashbuckle.AspNetCore

For Python:

MCP ref: "FastAPI OpenAPI documentation customization"
Context7: /tiangolo/fastapi

Key Patterns to Research:

  1. OpenAPI 3.0/3.1 specification
  2. Security scheme definitions
  3. XML comments integration (.NET)
  4. Response examples and schemas
  5. API versioning documentation

Phase 3: Decision Points

Q1: API Information

FieldDescriptionRequired
TitleAPI name✓ Yes
VersionAPI version (v1, v2)✓ Yes
DescriptionBrief descriptionOptional
ContactSupport contactOptional
LicenseAPI licenseOptional

Q2: Security Scheme

SchemeUse CaseOpenAPI Type
JWT Bearer (Recommended)Token in Authorization headerhttp + bearer
API KeyKey in header or queryapiKey
OAuth2Full OAuth2 flowoauth2
NonePublic APINo security

Q3: Documentation Features

Feature.NETPythonDefault
XML Comments✓ SupportedN/A✓ Enable
Response Examples✓ Manual✓ Pydantic✓ Enable
Request Validation✓ Annotations✓ Pydantic✓ Enable
Try It Out✓ Yes✓ Yes✓ Enable

Phase 4: Generate Configuration

.NET Output Files

FilePurpose
Extensions/SwaggerExtensions.csSwagger service registration
*.csproj (update)Enable XML documentation

Generation Process:

  1. Use MCP ref for current Swashbuckle API
  2. Generate SwaggerExtensions with:
    • AddEndpointsApiExplorer
    • AddSwaggerGen with OpenApiInfo
    • Security definition (if auth detected)
    • XML comments inclusion
  3. Update csproj for documentation generation

Packages to Add:

  • Swashbuckle.AspNetCore

Registration Code:

builder.Services.AddSwaggerServices();
// ...
app.UseSwaggerServices();

csproj Update:

<PropertyGroup>
  <GenerateDocumentationFile>true</GenerateDocumentationFile>
  <NoWarn>$(NoWarn);1591</NoWarn>
</PropertyGroup>

Python Output Files

FilePurpose
core/openapi_config.pyOpenAPI customization

Generation Process:

  1. Use MCP ref for FastAPI OpenAPI customization
  2. Generate openapi_config.py with:
    • Custom OpenAPI schema
    • Security scheme definitions
    • Tags and descriptions
  3. FastAPI generates OpenAPI automatically

Note: FastAPI has built-in OpenAPI support. This worker customizes the default configuration.

Registration Code:

from core.openapi_config import custom_openapi
app.openapi = lambda: custom_openapi(app)

Phase 5: Validate

Validation Steps:

  1. Syntax check:

    • .NET: dotnet build --no-restore
    • Python: python -m py_compile core/openapi_config.py
  2. Access documentation:

    StackURL
    .NEThttp://localhost:5000/swagger
    Pythonhttp://localhost:5000/docs
    Python (ReDoc)http://localhost:5000/redoc
  3. Verify content:

    • All endpoints visible
    • Request/response schemas displayed
    • Security scheme shown (if configured)
    • Try It Out functional
  4. OpenAPI spec validation:

    # .NET
    curl http://localhost:5000/swagger/v1/swagger.json | jq .
    
    # Python
    curl http://localhost:5000/openapi.json | jq .
    

Security Scheme Examples

JWT Bearer (.NET)

// Structure only - actual code generated via MCP ref
options.AddSecurityDefinition("Bearer", new OpenApiSecurityScheme
{
    Description = "JWT Authorization header using Bearer scheme",
    Name = "Authorization",
    In = ParameterLocation.Header,
    Type = SecuritySchemeType.Http,
    Scheme = "bearer",
    BearerFormat = "JWT"
});

JWT Bearer (Python/FastAPI)

# Structure only - actual code generated via MCP ref
from fastapi.security import HTTPBearer
security = HTTPBearer()

Return to Coordinator

{
  "status": "success",
  "files_created": [
    "Extensions/SwaggerExtensions.cs"
  ],
  "packages_added": [
    "Swashbuckle.AspNetCore"
  ],
  "registration_code": "builder.Services.AddSwaggerServices();",
  "message": "Configured Swagger/OpenAPI documentation"
}

Reference Links


Critical Rules

  • Use MCP ref for current Swashbuckle/FastAPI API — do not hardcode configuration from memory
  • Auto-detect auth scheme — scan for JWT, OAuth2, or API Key and configure security definition accordingly
  • Enable XML documentation in .NET — update csproj with GenerateDocumentationFile and suppress warning 1591
  • FastAPI: customize, not replace — built-in OpenAPI works by default, only add custom schema/security
  • Idempotent — if AddSwaggerGen/UseSwagger exists, return status: "skipped"

Definition of Done

  • Context Store received (stack, project root)
  • API structure analyzed (controllers/routers, auth method, versioning)
  • Documentation standards researched via MCP tools
  • Swagger/OpenAPI configuration generated with API info and security scheme
  • XML comments enabled (.NET) or custom OpenAPI schema configured (Python)
  • Syntax validated (dotnet build or py_compile)
  • Structured JSON response returned to ln-770 coordinator

Version: 2.0.0 Last Updated: 2026-01-10

Source

git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-775-api-docs-generator/SKILL.mdView on GitHub

Overview

Configures Swagger/OpenAPI documentation for .NET and Python APIs. It analyzes API structure, detects auth methods and versioning, and applies MCP-driven documentation standards to generate framework-specific configuration that powers OpenAPI docs and Try It Out.

How This Skill Works

The worker consumes the Context Store from ln-770, detects STACK and PROJECT_ROOT, and performs an idempotency check by scanning for existing Swagger/OpenAPI setup (AddSwaggerGen/UseSwagger in .NET or FastAPI defaults in Python). It then executes Phase 1 through Phase 5 to generate appropriate config files: .NET uses Extensions/SwaggerExtensions.cs and csproj updates, while Python creates core/openapi_config.py and registers app.openapi accordingly.

When to Use It

  • You maintain a .NET or Python API and need standardized OpenAPI documentation across services.
  • You want to enforce a consistent security model (JWT, API Key, OAuth2) in OpenAPI docs.
  • You need to enable or customize XML comments, response examples, and Try It Out in the generated docs.
  • You are integrating with MCP-driven documentation references for OpenAPI in either .NET or Python.
  • You prefer automated generation of framework-specific config files rather than manual setup.

Quick Start

  1. Step 1: Ensure Context Store from ln-770 provides STACK and PROJECT_ROOT, then trigger ln-775-api-docs-generator.
  2. Step 2: Let the tool analyze endpoints, auth, and versioning, then follow Phase 1–3 to decide config.
  3. Step 3: Review generated files (Extensions/SwaggerExtensions.cs and csproj for .NET or core/openapi_config.py for Python) and register the docs in your app.

Best Practices

  • Determine authentication method early (JWT, API Key, OAuth2) and mirror it in OpenAPI security schemes.
  • Ensure API metadata (Title, Version) is consistently defined and aligned with your versioning strategy.
  • Enable XML comments in .NET and meaningful response examples to improve doc quality.
  • Include request validation and versioning details as part of the OpenAPI spec.
  • Validate generated docs locally and via the Try It Out feature to catch non-public endpoints.

Example Use Cases

  • A .NET Core API using Swashbuckle with Extensions/SwaggerExtensions.cs and csproj updates to enable XML docs and OpenAPI generation.
  • A Python FastAPI project leveraging core/openapi_config.py to customize the OpenAPI schema and security definitions.
  • API using JWT Bearer tokens where the generated OpenAPI includes http bearer authentication in securitySchemes.
  • Versioned API with OpenAPI metadata reflecting v1, v2, and updated endpoints in the generated config.
  • Public API (None security) where the generator marks the API as public and omits security schemes.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers