contractslisted

Team baseline for external-interface contract artifacts: OpenAPI, JSON Schema, AsyncAPI, .proto, and GraphQL SDL, with spectral, ajv, buf, and graphql-inspector validation. Nudges devs toward contract-first artifacts; never writes them and never scaffolds a contracts/ directory. Auto-triggers for what contract should I use for this API, do we have an OpenAPI spec, add a JSON schema for this, recommend a schema for this endpoint, validate this API contract, or what's the right artifact for events. Defers to any other installed skill whose description identifies it as handling external-interface contract artifacts, API schema design, or contract-first workflow. Do not use for internal module-boundary refactoring, scaffolding a contracts/ directory, or auto-generating schemas from code.
ramboz/jig · ★ 4 · API & Backend · score 73

Install: claude install-skill ramboz/jig

> Spec 022 promoted this skill from a deliberate stub > ([ADR-0002](../../docs/decisions/adr-0002-contracts-stays-deferred.md)) > to jig's **team baseline** for external-interface contract artifacts, > following the reframing in > [ADR-0005](../../docs/decisions/adr-0005-contracts-as-judgment-skill.md). > Like `/jig:pr-review` (spec 012), `/jig:arch-review` (spec 014), and > `/jig:vision-elicitation` (spec 017), it ships as SKILL.md only — no > `.py` helper. The skill recommends the canonical industry-standard > schema per external surface and points at the ecosystem tools that > validate it. It does **not** write schemas, **not** scaffold a > `contracts/` directory, and **not** enforce contracts via PreToolUse > hooks. Enforcement is structural via the spec-author's first-pass > attention and the independent-review reviewer prompt's second-pass > check — both wired in slice 022-02. ## What this skill does For each external surface a project exposes (HTTP API, event bus, RPC, GraphQL, internal data shapes, CLI output, config), this skill recommends: 1. **The canonical artifact** — what to put on disk (e.g., `openapi.yaml`, `*.schema.json`, `*.proto`, `schema.graphql`). 2. **The validation tool** — what runs in CI to keep code and artifact in sync (e.g., `spectral lint`, `ajv validate`, `buf lint`, `graphql-inspector diff`). 3. **The codegen tool** — what produces typed clients / server stubs / TS types from the artifact, when ecosystem-appropriate (e.g., `op