openapi-spec-generation

Generate, maintain, and validate OpenAPI 3.1 specifications from codebases and design-first specs.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill openapi-spec-generation-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-spec-generation
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/openapi-spec-generation
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill openapi-spec-generation-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate, maintain, and validate OpenAPI 3.1 specifications from codebases, design-first specs, and validation patterns to ensure consistent API contracts and accurate documentation.

Core Features & Use Cases

  • Design-First: define API contracts before code and generate specs automatically.
  • Code-First / Hybrid: derive OpenAPI specs from code and annotate for evolving APIs; validate implementations against specs.
  • Templates & Validation: leverage templates for complete API specs, secure schemas, and multi-server configurations; validate correctness and interoperability.

Quick Start

Run the OpenAPI generation workflow against your codebase to produce a validated OpenAPI 3.1 specification.

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 OpenAPI 3.1 specifications from an existing codebase?

To generate OpenAPI 3.1 specifications from a codebase, you can use code-first workflows to derive specs directly from code and annotate evolving APIs to ensure accurate documentation and consistent API contracts.

What is the best way to validate API implementations against design-first OpenAPI specs?

Validating API implementations against design-first OpenAPI specs involves checking correctness and interoperability using validation patterns, ensuring your code matches the predefined API contracts and complies with OpenAPI 3.1 rules.

Can I use OpenAPI templates for multi-server configurations and secure schemas?

Yes, you can leverage reusable templates to define complete API specs, secure schemas, and multi-server configurations, ensuring consistent design patterns and security schemes across your OpenAPI 3.1 specifications.

Does design-first API development work for SDK generation and documentation portals?

Design-first API development defines API contracts before code, which directly supports automated SDK generation and accurate API documentation portals by enforcing consistent contracts across hybrid workflows.

How do I maintain OpenAPI 3.1 compliance for evolving APIs without losing validation rules?

Maintaining OpenAPI 3.1 compliance for evolving APIs requires using hybrid workflows to annotate code changes, validating implementations against specs, and applying enforced validation rules and security schemes throughout the process.