What problem does it solve? When frontend and backend teams or multiple services evolve an API or event schema independently, field names, nullability, enums, and error shapes drift apart, causing integration failures and silent breaking changes. This Skill establishes a single authoritative contract artifact that both consumers and providers verify against before integration. ## Core Features & Use Cases - Canonical Boundary Artifact: Defines one version-controlled source of truth per boundary using OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema. - Consumer-First Workflow: Guides teams through identifying consumers, describing consumer jobs, defining the smallest useful contract, generating types, and verifying provider responses against the same artifact. - Contract Change Protocol: Enforces a review process where the contract changes before implementation, with migration or versioning plans for breaking changes. - Use Case: A frontend team and a backend team build an orders feature in parallel. The consumer defines an OrderSummary schema in openapi.yaml, generates TypeScript types and mocks from it, and the provider proves its serialized responses satisfy the same schema before merge. ## Quick Start Ask the AI to define an OpenAPI contract for the endpoint your frontend and backend teams are building in parallel, then generate consumer types and verify provider responses against it.
