Enforce OpenAPI schema rules 14-24 for consistent API specifications.
npx skills add https://github.com/zerobias-org/module --skill openapi-schemas
Please help me install this Agent Skill. Skill: openapi-schemas Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/openapi-schemas Command: npx skills add https://github.com/zerobias-org/module --skill openapi-schemas
OpenAPI schema design often drifts from core rules, leading to inconsistent response mappings, inline objects, and duplicated definitions. This Skill codifies rules 14-24 to ensure stable, reusable schemas across APIs.
Define a User schema with both a summary and a full version using allOf to compose properties.
High-intent search queries and answers about installing and using this skill.
OpenAPI schema design consistency is enforced by codifying rules 14-24, which mandate direct main-object mapping via $ref, string IDs, no nullable fields, and proper nested references across API suites to prevent schema drift and duplicated definitions.
Summary and full schemas in OpenAPI are separated by splitting definitions and using allOf composition, allowing direct responses to reference lightweight summary objects while nested responses resolve into full, detailed business objects.
Using $ref for nested objects in OpenAPI enforces nested object discipline, ensuring maintainability and reusability by preventing inline object definitions that cause schema duplication and drift across API specifications.
Composing OpenAPI schemas using allOf involves defining a base User schema and extending it into summary and full versions, applying base composition rules to reuse shared properties while avoiding nullable fields and maintaining clean resource paths.
No, strict OpenAPI schema validation rules explicitly prohibit nullable fields and require string IDs to maintain clean resource paths and stable response mappings, ensuring consistent API specifications across the suite.
Context separation in OpenAPI schema definitions is needed when APIs require distinct nested and direct responses, allowing you to optimize payload size by returning summary schemas for lists and full schemas for detailed resource endpoints.
jtgironAlign Zod schema definitions, parsing flow, and inferred types in TypeScript projects.
pr-pmReplace TypeScript any types with interfaces, type guards, and generic constraints.
musher-devAudit OpenAPI specifications for inline schema anti-patterns and enforce component reuse.
zagarlucasGenerate OpenAPI 3.0/3.1 specifications for REST APIs with reusable components.
