Explainer
Vibe coding for kids, explained
"Vibe coding" is a new name for an old dream: you say what you want, and the computer builds it. Grown-up programmers now work this way with AI every day. Here's what it looks like when a kid is in charge.
What actually happens
- Your kid types an idea. "Make the sky purple." "Add a dragon that chases me." Plain words, any length.
- The AI helper writes the code. It changes the game's JavaScript, then says in one or two sentences what it did.
- The game updates beside the chat. They play it right away and notice what's off.
- They ask for the next change. Too fast? Wrong color? They say so, and the loop starts again.
Same idea, two ways
Here's one change, written as a kid would say it and as the code the helper writes. Your kid sees the result straight away, and can open Talk mode to ask what the code means.
"Make the sky purple and the hero jump higher"
sky.color = "#7a4dff";
hero.jumpPower = 14; // was 10
What your kid still does
The AI types the code, but the thinking stays with your kid. They choose the idea, break it into steps, describe each one clearly, test the result and decide what to fix. Those are the parts programmers spend most of their day on, too.
Kids meet real terms along the way, like variable, loop and condition, each explained in a line the first time it comes up. We don't promise it turns anyone into a programmer. It gives them a place to make things and see how software behaves.
Where it falls short
Big ideas sometimes come out different from what your kid pictured, and the helper occasionally gets things wrong. That's part of the loop: they say what's off, and it tries again. The helper has a set amount of building energy that refills on its own, so a long session pauses until the helper has rested.
Questions parents ask
Is vibe coding real coding?
The helper writes real JavaScript, and your kid decides what it should do, tests it and asks for fixes. They don't type the syntax themselves, so think of it as directing a programmer, with the ideas of programming in plain view.
Does my kid need to read well?
Short sentences are enough. Kids who are still learning to read can tap ready-made ideas, and a grown-up nearby helps for the first few sessions. Our guide for ages 6 to 8 has tips.
Will it replace learning to type code?
It doesn't have to. Many kids who build by describing later get curious about the code itself. See block coding vs. AI coding for how the two fit together.