AAWEA.ORG

Manual start

↓

1

Run contract tests

Run contract tests against openapi.yaml or schema fixtures. List every mismatch with endpoint and field.

> npm run test:contract
2

Fix implementation or spec

Fix the smallest change: update handler types/validation or correct the spec if the code is canonical.

↓

✓

Exit condition: tests_pass

All API contract tests pass

> npm run test:contract

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Run contract tests") S1("Fix implementation or spec") S0 --> S1 Exit{"All API contract tests pass"} S1 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "API Contract Until Match" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "API Contract Until Match" loop.

Goal: API implementation matches the published contract
Max iterations: 10
Between iterations run: npm run test:contract
Exit when: contract test suite exits 0

Step 1: Run contract tests. Fix each schema/response mismatch with minimal diffs, then re-run.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics