openapi-swagger-codegen-expert

OpenAPI & Swagger Codegen Expert (Contract-First 2026)

English | Bahasa Indonesia

---

English

Orchestration & Integration

• Upstream Specs & Design: api-design-expert, spec-driven-development-expert, prd-architect
• Frontend Consuming: tanstack-query-expert, senior-frontend, form-validation-expert
• Backend & Drifts: js-backend-expert, autonomous-api-drift-healer, api-gateway-proxy-expert
• CI/CD Quality & Security: ci-cd-devops-architect, e2e-testing-expert, anti-slop
• Lifecycle: zero-to-prod-orchestrator, session-memory-manager

Description

Dedicated expert guide for API contract-first development using OpenAPI 3.1 (with full JSON Schema 2020-12 alignment), interactive documentation (Scalar, Swagger UI, Redoc), and automated end-to-end client code generation. Covers generating strictly typed SDKs using openapi-typescript and openapi-fetch, creating automatic TanStack Query v5 hooks with Orval, scaffolding multi-language SDKs with Microsoft Kiota, and enforcing API design governance via Spectral in CI/CD pipelines.

Trigger Conditions

• Scaffolding modern RESTful API contracts before writing server code (Phase 1/4).
• Generating type-safe frontend API clients and TanStack Query hooks.
• Configuring interactive API documentation with Scalar or Swagger UI.
• Setting up automated contract testing with Prism or Pact.
• Migrating manual, unvalidated fetch() calls to auto-generated typed clients.

Production OpenAPI 3.1 Specification Example

# specs/openapi.yaml
openapi: 3.1.0
info:
  title: Vibes Core Service API
  version: 1.0.0
  description: High-scale contract-first API with strict schema validation.
servers:
  - url: https://api.vibesplug.internal/v1
    description: Production Cluster
paths:
  /orders:
    post:
      operationId: createOrder
      summary: Place an atomic order
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateOrderRequest'
      responses:
        '201':
          description: Order created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OrderResponse'
        '400':
          $ref: '#/components/responses/ValidationError'

components:
  schemas:
    CreateOrderRequest:
      type: object
      required: [customerId, items, totalCents]
      properties:
        customerId:
          type: string
          format: uuid
        items:
          type: array
          items:
            type: object
            required: [productId, quantity]
            properties:
              productId: { type: string }
              quantity: { type: integer, minimum: 1 }
        totalCents:
          type: integer
          minimum: 1
    OrderResponse:
      type: object
      required: [id, status, createdAt]
      properties:
        id: { type: string, format: uuid }
        status: { type: string, enum: [PENDING, PAID, FULFILLED] }
        createdAt: { type: string, format: date-time }