701-technologies-openapi

# OpenAPI 3.x best practices Help teams produce maintainable **OpenAPI 3.x** contracts that stay aligned with HTTP semantics and consumer needs. **What is covered in this Skill?** - Document structure: `openapi`, `info`, `servers`, `tags`, and consistent resource grouping - Path and operation design: parameters, request bodies, response matrices, `operationId`, status codes - Reusable `components` (schemas, parameters, responses, security schemes) and examples - Validation and CI: spec linting, breaking-change checks, pre-codegen gates - Security modeling in the contract (schemes, scopes, global vs operation security) - Clear boundaries between contract-first design and runtime implementation concerns **Scope:** Contract-first quality only. Focus this skill on OpenAPI design, quality, and governance guidance. ## Constraints Keep recommendations at the OpenAPI layer unless the user explicitly asks for Java framework integration. After editing this repository's XML sources, regenerate skills and verify the build. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before proposing Java or Maven changes in the same change set - **FRAMEWORK**: Keep guidance contract-centric; do not prescribe framework-specific controller wiring or runtime exposure details - **FUZZING**: Keep fuzzing guidance high-level and contract-focused without linking to external skill identifiers - **MANDATORY**: Regenerate skills with `./mvnw clean install -pl skills-generator` after editing skill...