Individual skill
contract-first
Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema), with generated consumer types and contract-verified integration. Use when parallel consumer and provider work must evolve an API or event schema without field drift, mock/production shape mismatch, or one side silently redefining the interface.
pi/core/skills/contract-first/SKILL.md
Source commit b38be6a7f6350964d59328b52f0624e1d1d552d1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 299,612
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- anthropic Repository topic
- claude Repository topic
- claude-code Repository topic
- developer-tools Repository topic
- llm Repository topic
- mcp Repository topic
- productivity Repository topic
- legal Derived category
- docs Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Contract-First Collaboration
Coordinate frontend/backend or service-to-service work through one authoritative,
machine-checkable contract. Consumers state what they need, providers implement
that shape, and both sides verify against the same artifact before integration.
This skill governs how teams change a boundary. It complements `api-design`,
which governs what a good API looks like, and `ai-regression-testing`, which
guards fixed bugs from returning.
## When to Activate
- Frontend and backend work will proceed in parallel.
- Two or more services exchange API payloads, events, or commands.