ai-contracts-workflow

Coordinate cross-boundary contract changes across server and SDK repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/eugene-belkovich/ai-setup --skill ai-contracts-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-contracts-workflow
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/claude/profiles/work/skills/workflow/ai-contracts-workflow
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill ai-contracts-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ai-contracts is the single source of truth for request/response types shared between the Chaos AI backend and SDK. You edit JSON Schema, and the toolchain generates TypeScript types, Zod schemas, and Python Pydantic models.

Core Features & Use Cases

  • Cross-repo contract alignment and validation across ai-contracts and ai-sdk workflows.
  • Trigger and coordinate the PR chain (ai-contracts → ai-sdk-workspace → ai-frontend) for every change.
  • Protect against breaking changes with diffs, pre-commit checks, and automated generation.

Quick Start

Review and apply contract changes across server and SDK using the established PR chain.

Frequently Asked Questions about ai-contracts-workflow

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

FAQPage Schema
How do I coordinate cross-boundary contract changes across server and SDK?

To coordinate cross-boundary contract changes, edit JSON Schema definitions in ai-contracts and trigger the PR chain workflow to update SDK references, regenerate types, and run diffs across server and SDK boundaries.

What is the PR chain workflow for shared schema definitions?

The PR chain workflow is a coordinated sequence: edit contracts, update SDK references, regenerate TypeScript and Python types, run diffs, and coordinate downstream consumers like ai-frontend.

How do I generate TypeScript and Python types from JSON Schema?

You generate TypeScript, Zod schemas, and Python Pydantic models by editing JSON Schema in ai-contracts, which acts as the single source of truth, and running the toolchain to automate type generation.

How do I protect against breaking changes when modifying shared types?

To protect against breaking changes when modifying shared types, run diffs, use pre-commit checks, and enforce the automated PR chain workflow across ai-contracts and ai-sdk-workspace repositories.

When do I need to trigger contract alignment validation?

You need to trigger contract alignment validation when modifying primitives, blocks, messages, or any shared types that cross the server/SDK boundary in ai-contracts or ai-agents-workflows.

Does this workflow support generating Python Pydantic models from JSON Schema?

Yes, the workflow supports generating Python Pydantic models from JSON Schema, alongside TypeScript types and Zod schemas, ensuring cross-repo contract alignment across server and SDK.