How Khelzy builds a playable game from one sentence

The obvious approach, and why we don't use it

The obvious way to build "AI makes you a game" is to have the AI write the game's code from scratch, every time. Sometimes that produces magic. Often it produces a game where the jump button works on Tuesdays. Code written fresh each time can fail in fresh ways each time — and nobody checks it before it reaches you.

We split the job in two instead.

The AI writes the recipe, not the kitchen

When you type "a fruit-slicing reflex game with juicy splashes," Khelzy's AI doesn't write a program. It writes a game plan — a precise description of your game: what kind of game it is, how fast things move, how many lives you get, what the obstacles are, what it should look like. Think of it as a recipe card with strict blanks to fill in.

That plan is then checked, line by line, by software — not by an AI — before anything runs. Speed out of range? Rejected. A rule the game can't actually support? Rejected. Only a plan that passes every check moves forward.

One engine, built by hand, runs everything

The checked plan is handed to the Khelzy engine — the "kitchen" — which we built and tested ourselves. The engine is deterministic: given a valid plan, it always produces a working game. The physics, the controls, the scoring, the game-over screen — all of that is our hand-written, battle-tested code. The AI never touches it.

So the AI contributes the creativity (what your game is), and the engine contributes the reliability (that your game works). That division is the whole secret. It's why every game in the feed loads in seconds and plays at full speed on an ordinary phone — and why a published Khelzy game is never a broken one.

It also keeps the AI honest

A nice side effect: because the AI must work within what the engine supports, it can't bluff. If your request is ambiguous, it asks you a quick question instead of guessing. If you ask for something the engine can't do yet, it says so and offers the closest thing it can build — rather than shipping you something quietly broken. And if the AI art (painted by an image model after your game is already playable) fails, the game keeps its clean built-in look. Failed generations are never charged.

Remixing falls out for free

Because every game is a plan and not a pile of code, anyone can remix a published game: take the plan, change what you want, republish — with the original creator credited automatically. Same reliability, new idea on top.

That's the machine. One sentence in, one working game out — try it yourself.