Fix Invalid JSON from AI
The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.
View Resource →Paste an AI's output and validate it against the expected format — with a repair prompt for every failure found.
The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.
View Resource →Paste the response, get the verdict: real JSON parsing, missing-field detection, and a repair prompt for everything found.
View Resource →The model answered "Complaints" — your set says "Complaint". One character of drift, one broken dashboard. Caught before it counts.
View Resource →The PRD looks done — but Non-Goals is gone and Requirements jumped above Goals. Section presence and order, checked in one pass.
View Resource →Run 40 looks nothing like run 1: sections reordered, one came back empty. Detect the drift, repair the run, keep the pipeline honest.
View Resource →Don't re-roll the whole response — send back a surgical prompt that fixes the violations and keeps everything that was right.
View Resource →Label in the set? Case exact? Confidence in range? The checks that keep classification output usable for routing.
View Resource →Heading scan against the skeleton: missing sections, broken order, absent title — the README that shipped without its Examples.
View Resource →Fields checked against the contract: missing ones flagged, invented ones caught, prose around the object detected.
View Resource →Did the summary keep its contract? Section presence, preamble detection, and the "Here is the summary" tax — checked and repaired.
View Resource →