What problem does it solve? Teams that write handler code before defining the API end up with contracts designed by accident — the API becomes whatever was convenient to implement rather than what consumers need. This Skill enforces a contract-first workflow where the OpenAPI spec or .proto file is written, linted, reviewed, and approved before any handler code exists. ## Core Features & Use Cases - Contract Generation: Produces a complete OpenAPI 3.1 YAML spec (with RFC 9457 error shapes, pagination, auth schemes) or a versioned .proto file following Google's protobuf style rules. - Linting and Mocking: Sets up a Spectral ruleset for spec linting in CI and a Prism mock server so frontend and backend teams develop in parallel against the same contract. - Review Gates: Dispatches an api-contract-reviewer agent and enforces a human approval gate before handler implementation begins. - Use Case: When a plan adds a new REST endpoint, run this Skill to produce api/openapi.yaml, wire Spectral into CI, start a Prism mock on port 4010, and only begin handler coding after the spec passes review. ## Quick Start Ask the AI to write the OpenAPI contract for the new endpoint defined in the plan before any handler code is written.