Generating API Contracts
Overview
Generate OpenAPI 3.0/3.1 specifications and consumer-driven contract tests from existing API implementations, design documents, or database schemas. Produce machine-readable contracts that serve as the single source of truth for code generation, documentation, testing, and gateway configuration, with Pact integration for consumer-driven contract verification.
Prerequisites
- API implementation with route definitions and handler logic, or design requirements document
- OpenAPI authoring tool: Swagger Editor, Stoplight Studio, or IDE with OpenAPI extension
- Consumer-driven contract framework: Pact (polyglot), Spring Cloud Contract (Java), or Dredd (generic)
- Schema validation tool: Spectral for OpenAPI linting
- Version control for contract files with diff-based review process
Instructions
- Scan existing route handlers and controller files using Grep and Read to extract all endpoint paths, HTTP methods, request parameter names/types, and response body shapes.
- Generate OpenAPI 3.0 specification from the extracted data, including
info (title, version, description), servers (environment URLs), paths (operations), and components (reusable schemas).
- Define request schemas with field-level constraints:
type, format, required, minimum/maximum, pattern (regex), enum, and example values for every property.
- Document all response status codes per endpoint with separate schemas: 200/201 for success, 400 for validation errors (with field-level error array), 401/403 for auth failures, and 404/500.
- Add security scheme definitions (
bearerAuth, apiKey, oauth2) and apply them to appropriate operations using the security field.
- Create Pact consumer contract tests that capture expected interactions from the API consumer perspective, defining expected request/response pairs per endpoint.
- Set up provider verification that replays Pact interactions against the actual API implementation, verifying the provider satisfies all consumer expectations.
- Generate contract artifacts: OpenAPI spec file, Postman collection, and consumer contract (Pact JSON), all versioned alongside the API source code.
See ${CLAUDE_SKILL_DIR}/references/implementation.md for the full implementation guide.
Output
${CLAUDE_SKILL_DIR}/openapi.yaml - Complete OpenAPI 3.0/3.1 specification${CLAUDE_SKILL_DIR}/contracts/pact/ - Consumer-driven contract definitions (Pact JSON)${CLAUDE_SKILL_DIR}/contracts/postman/ - Generated Postman collection for API testing${CLAUDE_SKILL_DIR}/tests/contract/consumer/ - Consumer contract test implementations${CLAUDE_SKILL_DIR}/tests/contract/provider/ - Provider verification test suite${CLAUDE_SKILL_DIR}/scripts/generate-contract.sh - Contract generation automation script
Error Handling
| Error |
Cause |
Solution |
| Spec-code divergence |
API implementation changed without updating the OpenAPI spec |
Add CI check that generates spec from code and diffs against committed spec |
| Pact verification failure |
Provider response does not match consumer expectation |
Review consumer contract for correctness; update provider if contract is valid |
| Missing operation ID |
Endpoint has no operationId, preventing code generation |
Generate deterministic operation IDs from method + path (e.g., getUsers, createUser) |
| Circular schema reference |
Components reference each other creating infinite recursion |
Break cycles with allOf composition or introduce intermediate types |
| Example/schema mismatch |
Example values do not validate against their own schema |
Auto-validate all examples during spec generation; reject mismatched examples |
Refer to ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error patterns.
Examples
Code-first OpenAPI generation: Scan Express route decorators and Zod validation schemas to auto-generate a complete OpenAPI 3.1 spec with accurate request/response schemas, examples, and descriptions.
Consumer-driven contract testing: Frontend team publishes Pact contracts defining the API interactions they depend on; backend CI verifies every contract on each deployment, preventing breaking changes.
Design-first workflow: Author OpenAPI spec in Stoplight Studio, generate server stubs and client SDKs from the spec, then implement business logic in the stubs -- spec stays as the single source of truth.
See ${CLAUDE_SKILL_DIR}/references/examples.md for additional examples.
Resources
1---2name: generating-api-contracts3description: Generate API contracts and OpenAPI specifications from code or design documents. Use when documenting API contracts and specifications. Trigger with phrases like "generate API contract", "create OpenAPI spec", or "document API contract".4license: MIT5---6# Generating API Contracts
7
8## Overview
9
10Generate OpenAPI 3.0/3.1 specifications and consumer-driven contract tests from existing API implementations, design documents, or database schemas. Produce machine-readable contracts that serve as the single source of truth for code generation, documentation, testing, and gateway configuration, with Pact integration for consumer-driven contract verification.
11
12## Prerequisites
13
14- API implementation with route definitions and handler logic, or design requirements document
15- OpenAPI authoring tool: Swagger Editor, Stoplight Studio, or IDE with OpenAPI extension
16- Consumer-driven contract framework: Pact (polyglot), Spring Cloud Contract (Java), or Dredd (generic)
17- Schema validation tool: Spectral for OpenAPI linting
18- Version control for contract files with diff-based review process
19
20## Instructions
21
221. Scan existing route handlers and controller files using Grep and Read to extract all endpoint paths, HTTP methods, request parameter names/types, and response body shapes.
232. Generate OpenAPI 3.0 specification from the extracted data, including `info` (title, version, description), `servers` (environment URLs), `paths` (operations), and `components` (reusable schemas).
243. Define request schemas with field-level constraints: `type`, `format`, `required`, `minimum/maximum`, `pattern` (regex), `enum`, and `example` values for every property.
254. Document all response status codes per endpoint with separate schemas: 200/201 for success, 400 for validation errors (with field-level error array), 401/403 for auth failures, and 404/500.
265. Add security scheme definitions (`bearerAuth`, `apiKey`, `oauth2`) and apply them to appropriate operations using the `security` field.
276. Create Pact consumer contract tests that capture expected interactions from the API consumer perspective, defining expected request/response pairs per endpoint.
287. Set up provider verification that replays Pact interactions against the actual API implementation, verifying the provider satisfies all consumer expectations.
298. Generate contract artifacts: OpenAPI spec file, Postman collection, and consumer contract (Pact JSON), all versioned alongside the API source code.
30
31See `${CLAUDE_SKILL_DIR}/references/implementation.md` for the full implementation guide.
32
33## Output
34
35- `${CLAUDE_SKILL_DIR}/openapi.yaml` - Complete OpenAPI 3.0/3.1 specification
36- `${CLAUDE_SKILL_DIR}/contracts/pact/` - Consumer-driven contract definitions (Pact JSON)
37- `${CLAUDE_SKILL_DIR}/contracts/postman/` - Generated Postman collection for API testing
38- `${CLAUDE_SKILL_DIR}/tests/contract/consumer/` - Consumer contract test implementations
39- `${CLAUDE_SKILL_DIR}/tests/contract/provider/` - Provider verification test suite
40- `${CLAUDE_SKILL_DIR}/scripts/generate-contract.sh` - Contract generation automation script
41
42## Error Handling
43
44| Error | Cause | Solution |
45|-------|-------|----------|
46| Spec-code divergence | API implementation changed without updating the OpenAPI spec | Add CI check that generates spec from code and diffs against committed spec |
47| Pact verification failure | Provider response does not match consumer expectation | Review consumer contract for correctness; update provider if contract is valid |
48| Missing operation ID | Endpoint has no `operationId`, preventing code generation | Generate deterministic operation IDs from method + path (e.g., `getUsers`, `createUser`) |
49| Circular schema reference | Components reference each other creating infinite recursion | Break cycles with `allOf` composition or introduce intermediate types |
50| Example/schema mismatch | Example values do not validate against their own schema | Auto-validate all examples during spec generation; reject mismatched examples |
51
52Refer to `${CLAUDE_SKILL_DIR}/references/errors.md` for comprehensive error patterns.
53
54## Examples
55
56**Code-first OpenAPI generation**: Scan Express route decorators and Zod validation schemas to auto-generate a complete OpenAPI 3.1 spec with accurate request/response schemas, examples, and descriptions.
57
58**Consumer-driven contract testing**: Frontend team publishes Pact contracts defining the API interactions they depend on; backend CI verifies every contract on each deployment, preventing breaking changes.
59
60**Design-first workflow**: Author OpenAPI spec in Stoplight Studio, generate server stubs and client SDKs from the spec, then implement business logic in the stubs -- spec stays as the single source of truth.
61
62See `${CLAUDE_SKILL_DIR}/references/examples.md` for additional examples.
63
64## Resources
65
66- OpenAPI Specification 3.1: https://spec.openapis.org/oas/v3.1.0
67- Pact contract testing: https://pact.io/
68- Swagger Editor: https://editor.swagger.io/
69- Dredd API contract testing: https://dredd.org/
micsapp