Building Worlds Together: The Delamor Family Guide to Vibe-Coding

For parents, tutors, and guides. And for the young architects beside them.

Welcome

In the Delamor curriculum there is a room called Imagination Studio: protected, child-led time where children build, design, invent, and pretend in whatever medium their current season of passion demands. Lego, clay, Minecraft, cardboard, costumes, maps, miniature worlds. The Studio has many tables, all set, none required, and its full philosophy lives in its own overview guide.

This guide is the field manual for one of those tables: the Code Table. For the child whose season is pointing at screens, or the family curious about the newest way to build, each week carries a rich standing invitation tied to the year's art, architecture, history, and geography. Your child does not fill in a page about ancient Rome. They build the aqueduct, and the water must truly flow downhill.

They do it by talking. Describing. Imagining out loud while an AI collaborator turns their words into a working creation on the screen: a game, a simulation, a world. No syntax. No typing lessons. No prior experience, for the child or for you.

This is called vibe-coding, and this guide will teach you both how to do it. Not by making you a programmer. By showing you a posture.

One promise before we begin: your child does not need you to know how this works. Your child needs you to be curious next to them. That is the whole job. Everything else in this guide is detail.

Part One: What Vibe-Coding Actually Is

Vibe-coding means describing what you want in ordinary language and shaping the result through conversation. The child says, "I want a pyramid that I build block by block, and each layer needs the right number of blocks." The AI writes the code. Something appears on the screen. The child looks at it and says, "The blocks are too small. And I want the sky to be sunset." It changes. They look again. They ask again.

That loop, describe, look, respond, describe again, is the entire method. It is also, if you look closely, the entire creative process of every architect, author, and inventor in your child's history workbook. Imagine, attempt, observe, revise. Vibe-coding just makes the loop fast enough for an eight-year-old's attention and vivid enough for their delight.

What children actually learn

They are not learning to code, exactly. They are learning something underneath coding:

Precision of thought. "Make it cooler" produces nothing useful. "Make the water flow downhill from the mountain to the fountain" produces an aqueduct. Children discover, fast, that clear thinking gets rewarded with a clear result. No worksheet teaches this half as well.

Decomposition. Big dreams break into small pieces. A castle is walls, then a gate, then a moat, then a dragon if there is time. Children learn to sequence their imagination.

Revision without shame. The first version is never the final version, and nobody expects it to be. This may be the most healing lesson in the whole studio, especially for children who have learned to fear being wrong.

Agency. The build exists because they described it. Their words did that. For a child who has mostly experienced learning as something done to them, this is a quiet revolution.

What this is not

It is not screen time in the passive sense. Watching a video and directing a build are as different as watching soccer and playing it.

It is not a shortcut around learning. The history is in the build. A child who spends an hour getting the beacon fires on their Great Wall to signal tower to tower has thought harder about Chinese frontier defense than most adults ever have.

And it is not a replacement for hands, paper, clay, and dirt. Imagination Studio is one day. The other days still smell like paint.

Part Two: Your Role as the Guide

Here is the secret that makes everything else work: you sit beside, not behind.

Behind is the posture of supervision. Beside is the posture of adventure. Your child can feel the difference in their spine.

The three things you actually do

1. You read the invitation aloud. Each week's build hook is written as an invitation, not an assignment. Read it like you are reading the opening of a story. Then ask the only question that matters: "What should it look like?"

2. You type their words, not yours. In the beginning, you may be the hands on the keyboard, especially with younger children. Resist every urge to improve their description on its way to the screen. If they say, "a pyramid but purple and huge," type exactly that. The build belongs to the one who imagined it. Your edits, however well meant, are small thefts of authorship.

3. You wonder out loud. Not instruct. Wonder. "Huh, I wonder why the water stopped there." "I wonder what happens if the layers get smaller as they go up." Wondering is contagious and it carries no pressure. Instructing ends the game. Wondering extends it.

The things you deliberately do not do

You do not fix it for them. You do not know the answer in advance, and when you accidentally do, you keep it in your pocket. You do not steer the build toward the version in your head. You do not say "we should" when you mean "I want."

If your child is a reluctant or demand-avoidant learner, this part is not optional garnish. It is the load-bearing wall. The moment Imagination Studio starts feeling like school wearing a costume, a perceptive child will see through it and close the door. The invitation must be real. Their "no" must be allowed. Some weeks the answer to the pyramid is "I want to build a volcano instead," and the correct curricular response is: magnificent, build the volcano. Egypt will still be there. The loop they are learning transfers to everything.

A word about your own discomfort

At some point, probably in the first ten minutes, your child will ask the AI for something and you will have no idea whether it is possible. Good. Say so. "I have no idea. Let's find out." A parent who models curiosity in the face of not-knowing teaches more in that sentence than a parent who knows everything teaches in a year. Your child gets to watch an adult learn. That sight is rarer and more valuable than we admit.

Part Three: How a Session Works

Before you start, once ever

You need three things:

1. A device with a browser. Laptop or tablet. A keyboard helps once descriptions get long.
2. An AI collaborator that can build. You want one that can generate working, interactive creations in the conversation itself, so your child sees their words become a running build without any setup. Set the account up yourself in advance so the first session starts with imagination, not passwords.
3. A ritual. Small and yours. A snack that only appears on studio day. A candle. A silly announcement voice: "The Studio... is open." Ritual tells the nervous system this is play, and play is where the learning hides.

The shape of a session

A good session runs thirty to sixty minutes and moves through five beats. You do not need to enforce these. They happen on their own once you have done it twice.

Beat 1: The invitation. (2 minutes.) Read the week's hook aloud. Look at the pictures in the week's book pages together. Ask: what should it look like?

Beat 2: The first ask. (5 minutes.) Help your child say what they want in one or two sentences, then send it. Do not polish. The rough first ask is part of the method.

Beat 3: The loop. (20 to 40 minutes.) Something appears. It is partly right and partly wrong. This is the good part. Look, react, describe the change, send it. Around and around. Your job in this beat is mostly to laugh at the weird versions and wonder out loud at the stuck points.

Beat 4: The showing. (5 minutes.) Every build gets witnessed. Play their game. Let them beat you at it. Call someone. Screenshot it for the fridge or the family chat. Making is only half the meal; being seen is the other half.

Beat 5: The closing. (1 minute.) Stop before frustration and, when you can, stop mid-momentum, right when they have one more idea. "Save that idea for next week" is the sentence that guarantees they come back. Ending on hunger is a gift.

When it breaks

It will break. The water will flow uphill. The blocks will float. The whole screen will go blank. This is not the session failing. This is the session working.

The single most useful sentence in vibe-coding is: "Ask it why."

Type: "The water is flowing the wrong way, why?" The AI will explain, in words, what went wrong, and offer to fix it. Your child just watched a mistake become a conversation instead of a verdict. Do that forty times over a school year and you have quietly rebuilt their entire relationship with error. There is no worksheet on Earth that can do that.

Part Four: A Real Session, Beginning to End

Week 4. The Nile & Pyramids. The hook: a pyramid stacker, built block by block, where every layer needs the right number of blocks.

What follows is a lightly tidied transcript of the kind of session you can expect. Your child's version will be different, and better, because it will be theirs.

Parent: (book open to the Great Pyramid spread) Okay. Two million blocks, each one heavier than our car. What should ours look like?

Child: Big. And you have to build it yourself, you can't just get it. And it should tell you if you mess up a layer.

Parent: Say it to the Studio. I'll type.

Child: "Make a pyramid game where I place blocks one at a time. The bottom layer is 10 blocks wide. Each layer up is smaller. If I try to put a block in the wrong place it should wobble and fall off."

(A build appears: a flat brown pyramid on a white background, clickable blocks.)

Child: It works!! But it's ugly. It looks like chocolate.

Parent: (typing exactly this) "It looks like chocolate."

(The AI asks what look they want instead.)

Child: Sandstone. And desert behind it. And the sky should be sunset because that's when they stopped working.

(New version: golden blocks, orange sky, sand.)

Child: Ohhh. Okay now the wobble. Make a block fall off if it's floating.

(They test it. A floating block wobbles and tumbles. The child places it wrong on purpose four more times, laughing.)

Parent: I wonder how many blocks the whole thing takes.

Child: Wait. Ask it to count. "Show a counter of how many blocks I placed. And how many the real pyramid has."

(A counter appears: their 55 against 2,300,000.)

Child: That's insane. How long would that take me?

Parent: I genuinely don't know. Ask.

(The AI does the arithmetic with them: at their clicking speed, roughly a decade of nonstop clicking. The child sits back.)

Child: And they didn't even have clicking.

Parent: (letting the silence sit, because that sentence right there was the history lesson)

Child: Next week can I put a mummy inside it?

Parent: Save that idea for next week.

Session over. Thirty-five minutes. Notice what happened inside it: place-value math in the layer counts, scale and estimation in the block counter, historical empathy arriving unforced in one sentence, and an eight-year-old who cannot wait for the next history lesson. Nobody assigned any of that. It was all invited.

Part Five: Growing Through the Year

The weekly hooks are calibrated to grow with your child. Early Fall builds are single-idea builds: stack the blocks, paint the cave. By Winter, builds carry systems: signal fires that relay along the Great Wall, trade routes with gains and losses. By Spring, builds carry real logic: circuits, physics, a lunar lander. Your child will not notice the ramp. That is the point of a good ramp.

Two milestones to watch for and quietly celebrate:

The day they take the keyboard. Sometime midyear, most children start typing their own asks. Let it happen naturally. Your promotion from typist to witness is a graduation for both of you.

The day they go off-map. The week they ignore the hook and build their own idea entirely is not a discipline problem. It is the whole curriculum working. The hooks are training wheels for imagination. The bicycle was always the goal.

And Week 36 belongs to them completely: they choose their favorite era from the whole year and build the biggest thing they have ever built. By then, they will not need this guide. Neither will you.

Quick Reference: The Studio Card

Copy this page. Put it near the device.

The one question: What should it look like? The one rule: Type their words, not yours. The one move when stuck: Ask it why. The one way to end: Before frustration, on hunger. "Save that idea for next week." The one posture: Beside, not behind.

Say more of: I wonder... / Let's find out / Show me / What if Say less of: We should / That's not right / Let me do it / Are you sure

Remember: The build is theirs. The witnessing is yours. The wonder is shared.

Imagination Studio is part of the Delamor curriculum. One day a week, or however many days it takes them.