skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

ivt-openapi-spec

Align OpenAPI 3.x specifications with module structures and code contracts.

2|Updated Apr 11, 2026
Search Tags:#security#openapi#codebase#validation#swagger#tags#api-design
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill ivt-openapi-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ivt-openapi-spec
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/ivt-openapi-spec
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill ivt-openapi-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a principled approach to designing OpenAPI 3.x specs that reflect actual code structure and contracts across frameworks, ensuring consistent tagging, security definitions, and schema requirements.

Core Features & Use Cases

  • Derives meaningful tags from the codebase (module, router prefix, or domain) to keep APIs organized.
  • Enforces explicit required fields, requestBody structures, and proper security scheme declarations according to real guards.
  • Works across NestJS, Go, Python, and other stacks, with a project-language-aware guidance.

Quick Start

Create or adjust your OpenAPI 3.x spec so tags map to modules, paths reflect your routes, and security schemes match real guards.

Frequently Asked Questions about ivt-openapi-spec

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

FAQPage Schema
How do I align my OpenAPI spec tags with actual code module structure?▼

Align OpenAPI specification tags with codebase modules by deriving tags from router prefixes or domain boundaries, ensuring API documentation reflects real code organization and contract enforcement.

How do I match OpenAPI security schemes to implemented route guards?▼

Match OpenAPI security schemes to implemented guards by declaring explicit security definitions in the spec that correspond to actual authentication logic enforced within your codebase routes.

Does OpenAPI validation work across NestJS, Go, and Python stacks?▼

OpenAPI validation works across NestJS, Go, and Python stacks by applying project-language-aware guidance to enforce proper requestBody schemas, required fields, and error components per framework convention.

What is the best way to enforce required fields and requestBody schemas in Swagger?▼

Enforce required fields and requestBody schemas in Swagger by applying OpenAPI structure rules that mandate explicit declarations, ensuring component definitions match the data contracts implemented in code.

Why does my OpenAPI documentation show mismatched tags and paths?▼

OpenAPI documentation shows mismatched tags and paths when specs are not derived from the actual codebase structure, requiring alignment of routing prefixes and module domains to reflect real contracts.

How to structure OpenAPI components and error schemas for API design?▼

Structure OpenAPI components and error schemas by enforcing OpenAPI structure rules that mandate proper component declarations, ensuring consistent API design and valid specification validation across frameworks.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-zoom-out

Maps modules, primary callers, and key domain concepts from code.

Community
Intermediate
AcczdyAcczdy
2

implementing-api-schema-validation-security

Enforce OpenAPI v3.x request and response schema validation against JSON Schema contracts.

Community
Advanced
vladm3105vladm3105
16

contract-tester

Validate API contracts and detect breaking changes across OpenAPI/AsyncAPI specifications.

Community
Advanced
peopleforresterpeopleforrester
3

api-docs

...

Community
Intermediate