Menu
API contract validation patterns for ensuring client-side models match backend JSON responses. Tech-stack agnostic.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compressed-prose response style for the orchestrator (opt-in via behavior.caveman_mode). Drops articles, fillers, and transitional prose; preserves code, paths, JSON/TOML, and quoted text verbatim.
Maestro project patterns — Rust CLI with ratatui TUI, tokio async, Claude CLI process management, and stream-json parsing.
TEMPLATE - Backend API development patterns. Copy and customize for your backend framework (Express, Django, Spring Boot, FastAPI, etc.)
TEMPLATE - Frontend web development patterns. Copy and customize for your frontend framework (React, Vue, Angular, Svelte, etc.)
Defensive patterns for GitHub (gh) and Azure DevOps (az) CLI interactions — error handling, idempotency, rate limits, missing resources.
API contract validation patterns for ensuring client-side models match backend JSON responses. Prevents decoding failures from schema mismatches. Tech-stack agnostic.
| name | api-contract-validation |
| version | 2.0.0 |
| description | API contract validation patterns for ensuring client-side models match backend JSON responses. Tech-stack agnostic. |
| allowed-tools | Read, Grep, Glob, WebSearch |
Prevent bugs where client-side models don't match backend API responses.
docs/api-contracts/{feature}-{endpoint}.json
{
"$schema": "api-contract-v1",
"endpoint": "GET /api/items",
"description": "What this endpoint does",
"response": {
"items": {
"type": "array",
"items": {
"id": { "type": "string", "required": true },
"name": { "type": "string", "required": true }
}
}
}
}