openapi-spec-generation

Generate and maintain OpenAPI 3.1 specifications for RESTful APIs.

3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/DrLuggels/my_dhbw --skill openapi-spec-generation-drluggels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-spec-generation
Source: https://github.com/DrLuggels/my_dhbw/tree/main/.claude/plugins/documentation-generation/skills/openapi-spec-generation
Command: npx skills add https://github.com/DrLuggels/my_dhbw --skill openapi-spec-generation-drluggels

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of OpenAPI 3.1 specifications, ensuring consistency and accuracy for API documentation and development.

Core Features & Use Cases

  • API Specification Generation: Create OpenAPI 3.1 specs from code (code-first) or design (design-first).
  • Validation and Linting: Use tools like Spectral and Redocly to enforce standards and catch errors.
  • SDK Generation: Automatically generate client SDKs in various languages (TypeScript, Python, Go).
  • Use Case: When developing a new REST API, use this Skill to generate a comprehensive OpenAPI specification that can then be used to generate documentation, client libraries, and server stubs.

Quick Start

Use the openapi-spec-generation skill to generate a complete OpenAPI 3.1 specification for a user management API based on the provided template.

Frequently Asked Questions about openapi-spec-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an OpenAPI 3.1 specification from existing code?

You can generate an OpenAPI 3.1 specification from existing code using a code-first approach. This Skill supports extracting API documentation directly from Python/FastAPI and TypeScript/tsoa implementations to create comprehensive specs.

What is the difference between design-first and code-first API documentation?

Design-first API documentation defines the OpenAPI specification before writing code, while code-first generation extracts the spec from existing frameworks like FastAPI or tsoa. This Skill supports both approaches for RESTful APIs.

Can I validate and lint OpenAPI specifications using Spectral and Redocly?

Yes, you can validate and lint OpenAPI specifications using Spectral and Redocly. This Skill facilitates contract compliance validation and enforces standards to catch errors in your API documentation.

How do I generate client SDKs from an OpenAPI specification?

You can generate client SDKs from an OpenAPI specification by maintaining a comprehensive spec. This Skill facilitates automatic SDK generation in various languages including TypeScript, Python, and Go.

Does this approach work with TypeScript and Python for API spec generation?

Yes, this approach works with TypeScript and Python for API spec generation. The Skill provides code-first generation examples specifically for Python/FastAPI and TypeScript/tsoa frameworks to create OpenAPI 3.1 specs.

Why should I use a design-first approach for RESTful API development?

You should use a design-first approach for RESTful API development to ensure consistency and accuracy across API documentation. It allows you to validate contracts, generate server stubs, and create client libraries before implementation.