skills.rest
ramboz
rambozCOMMUNITY
Explore all skills by this author →
GitHub

contracts

Recommend canonical contract schemas and validate them with ecosystem tools.

5|Updated May 12, 2026
Search Tags:#openapi#validation#contracts#artifact#json-schema#spectral
One-click install
npx skills add https://github.com/ramboz/jig --skill contracts-ramboz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contracts
Source: https://github.com/ramboz/jig/tree/main/skills/contracts
Command: npx skills add https://github.com/ramboz/jig --skill contracts-ramboz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a consistent, discoverable baseline for external-interface contracts by guiding teams toward canonical artifacts and orchestrating ecosystem validation.

Core Features & Use Cases

  • Canonical artifact recommendations for each surface (OpenAPI for HTTP APIs, JSON Schema for internal data shapes, AsyncAPI for events, .proto for gRPC, GraphQL SDL).
  • Validation tooling orchestration (spectral, ajv, buf, graphql-inspector) to keep artifacts aligned with implementations.
  • Deferral mechanism to other installed skills whose descriptions indicate handling contract artifacts, API schema design, or contract-first workflows.
  • Explicit guidance to avoid writing or scaffolding a contracts/ directory; defers to established experts or other skills.

Quick Start

Ask Jig to select the appropriate external-interface contract artifact for your surface, such as OpenAPI for HTTP or JSON Schema for internal data shapes.

Frequently Asked Questions about contracts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What external-interface contract artifact should I use for my HTTP API or event schema?▼

OpenAPI is recommended for HTTP APIs, AsyncAPI for events, JSON Schema for internal data shapes, and GraphQL SDL for GraphQL interfaces. This guidance ensures external-interface contracts are discoverable and consistently structured.

How do I validate my OpenAPI or AsyncAPI contract artifacts against implementation?▼

Validate contract artifacts using ecosystem tools like Spectral, ajv, buf, and graphql-inspector. This orchestration keeps your external-interface schemas aligned with actual implementations across HTTP APIs, events, and gRPC.

Does this contract validation approach support gRPC and GraphQL surfaces?▼

Yes, it supports gRPC via .proto artifacts and GraphQL via SDL. It orchestrates validation using buf for gRPC and graphql-inspector for GraphQL, ensuring external-interface contracts remain aligned with implementations.

Can I use a specialized API schema design workflow instead of the baseline contract recommendations?▼

Yes, it defers to other installed skills whose descriptions indicate handling contract artifacts, API schema design, or contract-first workflows. This baseline only applies when a more specialized contract workflow does not exist.

Why should I avoid scaffolding a contracts directory directly for my API schemas?▼

You should avoid writing or scaffolding contracts directories directly because this baseline defers to established experts and other specialized skills for contract artifact generation, ensuring canonical schemas and proper ecosystem validation.

Related Skills

Explore More Software Engineering Skills→
tense-itense-i
1

openapi-spec-generation

Generate and maintain OpenAPI 3.1 specifications for RESTful APIs in YAML or JSON formats.

Community
Intermediate
rabbicserabbicse

api-testing

Validate REST and GraphQL API responses against expected contracts and behavior.

Community
Advanced
espensevespensev

mcp-server-patterns

Define and enforce MCP server patterns across SDKs, transports, and registrations.

Community
Advanced
GoldziherGoldziher
115

Code Generator Design - Spec-to-Handler Codegen

Generate type-safe API handler stubs and test fixtures from OpenAPI and AsyncAPI specifications.

Community
Advanced