Cursor-rules-java 701-technologies-openapi

Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. Part of the skills-for-java project

install
source · Clone the upstream repo
git clone https://github.com/jabrena/cursor-rules-java
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/jabrena/cursor-rules-java "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/701-technologies-openapi" ~/.claude/skills/jabrena-cursor-rules-java-701-technologies-openapi && rm -rf "$T"
manifest: skills/701-technologies-openapi/SKILL.md
source content

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 or system-prompt XML in this repo
  • VERIFY: Run
    ./mvnw clean verify
    or
    mvn clean verify
    before promoting changes

When to use this skill

  • Review an OpenAPI
  • Improve an OpenAPI
  • Improve API contract
  • Improve API schema design
  • Validate an OpenAPI spec

Reference

For detailed guidance, examples, and constraints, see references/701-technologies-openapi.md.