About Junior Prompters

It started with a game my son and I built together.

Not a course. Not a worksheet. An actual Roblox game — and then apps — that we made side by side at the kitchen table.

My kids had already been through the coding classes. Python. JavaScript. Months of lessons. And when we finally sat down to build something real, here's the honest truth: almost none of it came in handy. What actually worked was different. We'd describe what we wanted to create, prompt for it, and build it — piece by piece, together.

That was the moment it clicked. The hard part was never the syntax. It was knowing what you want to make — and having the tools to make it. And those tools had just changed completely.

What I watched happen next

Once my kids stopped memorizing code and started directing it, something shifted. They weren't following instructions anymore. They were making decisions. Designing worlds. Fixing their own bugs. Chasing their own ideas.

And then the best part: they didn't need me.

We still love building together — that's our thing, sitting down and making something as a team. But make no mistake about who's in charge. They have the lead. I'm the co-pilot when they want one, and completely unnecessary when they don't. That's exactly how it should be.

That's why Junior Prompters exists

I made the guide I wish we'd had at the start — the one that skips the months of syntax and gets straight to building something real.

It's for kids who want to make their own games and apps, not color inside someone else's lines. It's for the kid working solo who wants to build the thing in their head. And it's for families like mine who just like making stuff together — with the kid firmly in the driver's seat.

Junior Prompters treats kids like what they are: builders and directors.
Give them a vision and the right tools, and they'll surprise you every single time.

The tools leveled up. Now it's their turn to build something amazing.