Skip to content

· Thread

The machine that builds the product

We're not building the product anymore, we're building the machine that builds it: model, harness, context, tools, evals. Ours: ~60 min prompt to publish.

Originally posted on X · · View original (on X)

The job changed. We're not building the product anymore, we're building the machine that builds it: model, harness, context, tools, evals.

Ours: ~60 min prompt to publish. The machine alone needs ~35. The other 25? Unknown. Full-stack problem, no full-stack analytics.

What we can measure: every kit release runs three reference builds (simple, medium, complex) scored on UI consistency, content design, turns, time and tokens. Last run caught one hardcoded border radius that should have been a token. That's the harness layer. The rest is dark.

How we built our version of that machine, Kit to Studio to multiplayer:

Quoting @meidadmar

← Notebook · Case study