Engineering

Make your AI measure its game, not eyeball it: build, critique, measure, fix

Meticulai's loop for getting a coding agent to critique its own game work with numbers instead of 'looks good': a headless rules engine that replays any match from a seed and an action log, every complaint turned into a measured check, a separate critic that never grades its own homework, per-frame clipping counts over full AI-vs-AI matches, and before/after tables on the exact same checks.

CloneKit@clonekitaiCloneKit creator
Checked automatically · v1.0.0 · Oct 25

What your AI will deliver

  • A headless harness: the game's rules run with no rendering, every match is a seed plus an action log, and a replay check proves N replays end in identical state
  • RULES.md: the game's rules as a spec, with numbered checks the engine must match (test or bulk AI-vs-AI run per check)
  • A metrics catalog: every 'it feels off' complaint written as a number, how it is measured, the reference it is compared to and a target
  • A baseline report with those numbers over full auto-played matches

How it runs

In your AI, with your accounts. It starts by researching your business. How kits work ›

  1. 1. Understand

    Researches your business first, then asks you 5 questions it can't answer alone

  2. 2. Choose

    Nothing to choose: the kit follows one path

  3. 3. Build

    7 steps, risky ones ask you first

  4. 4. Deliver

    8 checks before delivery

Tools it uses

You pay each tool directly, not CloneKit. Your AI checks which ones you already have.

Details