Prompt generator Claude Code · Grok Build No gate, no limit, no truncation

Ratchet
Loop

A build loop where quality can only click forward. Say what you want built and what good looks like — this writes the prompt, captures your references, and hands back the run kit. Every round has to beat the round before it, not just the reference.

What is a Ratchet Loop

0 / 6 · advances only

Brief No — Spec sheet · every field reachable, none required but one
0 chars

Say what the finished thing has to achieve. Don’t prescribe the stack or the architecture — that caps the result at your own imagination. There is no length limit and nothing here is ever truncated; the field scrolls rather than pushing the page.

02 · The bar — what does good look like? no references

A bar has to be named, fetchable and comparable — something the agent can open, run, read or screenshot and put beside its own work. Leave it empty and the prompt makes finding one round zero’s only job.

One surface, three kinds. Drop a file here — or use any of these, all keyboard-reachable:

Typed path
The agent opens it directly — only when it runs on this machine.
Dropped file
The browser hands over the name only, never the folder. Give the folder once; it is kept for next time.
Uploaded
Becomes an https URL any agent can fetch, anywhere. Use this for anything shared with a team.
A URL
Captured here — desktop and mobile full-page screenshots plus the page as markdown. Real pixels, or a labelled blank.
  • Capture · Kind · Reference · StateThe bar is empty. Every reference you add rules a notch across this box — the literal string the agent is handed, whichever of the three tests it fails, and real pixels where a capture exists.
03 · Where it runs Claude Code
04 · Loop strength Gauntlet

Gauntlet by default on an empty brief; this line always says why, and picking a plate overrides it.

05 · Caps — optional, and you should no caps

Cost This family of methods routinely runs into hundreds of dollars. A promoting Ratchet round costs roughly 5–9× a plain Gauntlet round. Nothing here stops it but you — set a cap you are comfortable losing, and watch it.

06 · The sealed suite — the checks the loop does not write nothing sealed

Every other check gating your run is one the loop wrote, from your words. These are not. They run every round, and it may not read or edit them. How that works.

A sentence is enough. Round 0 builds the harness that demonstrates it; the sentence itself is sealed and the harness must fit it, never the reverse.

Nothing uploaded. A script is the strong version: nothing about it is interpreted, and a failure means the artifact changes.

A command, and where it serves. Without this, every invariant below reports unrunnable — which is not a pass, and the run is told to say so.

Invariants — ticked, never guessed

The second one writes a different, much shorter prompt: go and find three to five real references, propose the criteria with the measurement that decides each, propose the sealed suite, sketch what it would and would not build — then stop, so you can disagree before the money is spent. Cut what is wrong and bring it back here.

The filed brief

Unfiled 


        
        
Nothing filed yet.


          The prompt lands here — complete, self-contained, and never truncated at any length.
          It carries the invocation, the goal, the bar with every reference and how to obtain each,
          the loop mechanics, the harness primitives, the caps and the stop conditions.