Here's how to build self-evolving 3D games with Jev AI, one simple prompt at a time.
Imagine a game that studies how you play, and then builds new enemies designed to beat you.
It changes their legs, their armor and their attack after every single wave.
I'll also show you a planet you can talk to, and it rebuilds itself while you watch.
Jev makes all of those decisions in about one second, and the version I used is free.
Stick around, because I'm giving you every prompt I used, step by step.
What you're watching: my drone circles the island and clears wave one. The wave ends, Jev reads how I fought, and the cards show what it picked for wave two: burrowers, a front shell, acid spit and a lava world.
Harder is the same thing, just faster.
Jev changes what comes at you, based on how you play.
What you're watching: the real note my game wrote after one wave, word for word, and the eight answers Jev sent back in 1096 ms.
What you're watching: my autopilot plays like a sniper and only shoots from far away. Jev answers with burrowers: they dig under the floor where bullets can't reach, then pop up close.
What you're watching: the autopilot charges in and fights up close. When the note says the player is struggling, Jev switches to a green meadow that heals, slows the enemies down and hands over a triple-shot gift.
What you're watching: six sentences typed into the planet app. Each one is a single Jev call with six questions, and the planet animates whatever Jev picked: mountains, a meteor, forests, glowing cities, rings and a moon, volcanoes with a red sky.
What you're watching: three sentences. "What time is it" scores 18% and "this looks amazing" scores 30%, so the planet ignores both. "Freeze the whole planet" scores 93%, and the ice rolls in.
What you're watching: nobody is typing. Every few seconds the planet sends Jev its own stats and recent history, and Jev picks what nature does next. The age jumps forward millions of years each time.
Make a folder called jev-worlds and work inside it.
Write a tiny Node server called server.mjs, with no npm packages, on port 8088.
It does two things:
1. It serves the files in this folder as a website.
2. It has one route, POST /jev, that takes { state, questions } and forwards it to Jev, the free decision model, at https://opencode.ai/zen/v1/systemone with the body { model: "jev-1.13-free", state, questions }. No API key is needed. It returns Jev's answer to the browser.
Retry twice if Jev is slow, and save every decision to decisions.jsonl.
Then test it for real: send the state "A player keeps sniping from far away" with one choice question, "counter", with the options rushers, shielded and swarm. Show me Jev's answer.What you're watching: prompt 1 going into a brand-new Claude Code with no setup. It writes the server, starts it, and asks Jev its first real question. Done in 52 seconds.
Build a 3D arena shooter in evolve/index.html and evolve/game.js, using three.js from a CDN with an importmap. The world is a floating island made of hex tiles, with a sky gradient, fog, floating rocks in the distance and drifting particles. The player is a small hover drone with a spinning glowing ring. WASD moves it, it aims at the mouse and fires on its own, and Space dashes. Enemies walk in from the edge in waves. When a wave is dead, show a big GENERATION 2 banner and start the next wave. Add bloom, soft shadows and a health bar. Make it look premium, not like a pile of boxes.
What you're watching: prompt 2 in a clean Claude Code. It writes the page and the game, then screenshots its own game, looks at the pictures and fixes what looks wrong, again and again for about 19 minutes.
Make evolve/creatures.js. Every enemy is built from a genome: - movement: scuttle (six legs), hop (spring legs), glide (wings), or burrow (a drill that tunnels underground where it can't be shot) - armor: none, a front shell that blocks shots from the front, spikes, or split (it splits into two small ones when killed) - attack: bite, acid spit from range, or explode up close - size 0 to 4 and speed 0 to 4 Every gene must change how the creature LOOKS and how it BEHAVES. Spawn each wave from one genome, and add evolve/lab.html that shows eight different genomes side by side on turntables.
What you're watching: eight different gene lists, side by side. Legs for runners, spring legs for hoppers, wings for gliders, a drill for burrowers, plus shells, spikes and glowing acid sacs.
Make evolve/brain.js. After every wave, call POST /jev ONCE with 8 questions: - movement, armor and attack: choice questions, where each option's description says which kind of player it beats - size and speed: score questions with 5 labels (the criteria for a score must be a list) - the next world: meadow (slowly heals the player), ember (lava vents erupt), frost (slippery ice) or neon (dark) - the arena layout: pillars rise, the outer edge crumbles, or open - one gift for the player: triple shot, faster fire, shield, faster dash or piercing shots The state is plain English that describes how the player just fought. If Jev doesn't answer within 7 seconds, pick at random and label it "local" on screen, so it's never passed off as Jev.
While the player fights, measure: how far away they usually are when they kill, how close the nearest enemy gets, which way they circle the arena and how often, how long they stand still, how long they spend near the edge, their accuracy, how many shots bounced off shells, and how much damage each attack did to them. Write all of that into the plain-English state for Jev. When a wave ends: 1. Show "Jev is studying how you fought…" with a spinning DNA helix. 2. Deal eight cards, one per decision, each with how sure Jev was as a %. 3. Morph the world into the new biome in a wave that rolls out from the centre. 4. Apply the arena change and the gift, then hatch the new generation from the edge.
What you're watching: the moment a wave ends: Jev studies the player, eight cards deal out with how sure it was, the lava world rolls out from the middle, and the new generation hatches at the edge.
Add an autopilot: ?bot=sniper keeps its distance, ?bot=brawler fights up close, ?bot=circler runs in circles. Then playtest it yourself with headless Chrome, two minutes per style, and prove three things: 1. The game never freezes. 2. Jev designs different enemies for different styles. 3. No wave can get stuck: if a wave lasts 30 seconds, shells crack and burrowers come up. Fix anything that breaks, and show me what Jev picked for each style.
What you're watching: prompt 6 in a clean Claude Code. It adds sniper, brawler and circler bots and plays each style for two minutes against real Jev: no freezes, no stuck waves, zero errors, and different enemies per style. It also notes the very first redesign was the same for all three.
built only from prompts 1 to 6 · nobody touched the code · recorded in headless ChromeWhat you're watching: the game a clean Claude Code built from prompts 1 to 6 alone. Its own circler bot clears wave one, Jev decides all eight changes in 2 seconds, and the island turns into a neon world full of burrowing, shelled acid-spitters.
These games are the fun version. The same one-call decision step sorts leads, routes support tickets and picks the next action for your agents. Inside the AI Profit Boardroom you get the whole system it plugs into.
No. Everyday work runs on free local models and free APIs, and for the heavy work it drives the tools you already pay for, like the Claude subscription that already includes Claude Code.
Jev itself was free in every test on this page, and inside the Boardroom there are full token-saving tutorials.
Build planet/index.html and planet/planet.js: a low-poly 3D planet floating in space, with three.js. Faceted terrain from noise, a water sphere, a cloud layer, a glowing atmosphere, stars and a nebula. The planet can change in all of these ways: raise mountains, carve oceans, grow forests (instanced trees), spread deserts, freeze or melt ice, build glowing cities (instanced buildings), erupt volcanoes with lava and smoke, take a meteor hit that leaves a crater, get storms with lightning, and gain rings and moons. Every change animates over about two seconds. Nothing snaps.
What you're watching: prompt 7 in a clean Claude Code. It writes the planet, then screenshots every one of the twelve changes mid-animation and fixes what looks wrong. It finished with no console errors.
Add a text box, a microphone button (Web Speech API) and a row of example phrases. When I say something, call POST /jev ONCE with 6 questions: 1. is_command (noul): does the speaker want something to happen to the planet? 2. the main change: a choice from the list of planet changes 3. a second change, or none 4. where: here, north, south, east, west, equator or everywhere, measured from where the camera is looking 5. how big: a score with 5 labels 6. the sky colour: keep, blue, sunset, toxic, violet or crimson If is_command is under 0.5, change nothing and say "not a planet command". Otherwise fly the camera to the spot and apply the change. Show every decision with its % in a panel.
What you're watching: prompt 8 in a clean Claude Code. It tests Jev's question format first, wires the text box, mic and example phrases, then checks typed commands end to end against real Jev.
Add a "Let it evolve on its own" switch. Every 16 seconds with no input, send Jev the planet's stats (land, ocean, forest, desert, ice, cities, temperature, moons), its age, and the last six events. Ask what nature does next (eruption, mountains, forest, desert, ice age, warming, sea rise, cities grow, meteor or storm), where, and how big. Apply it, add about 50 million years to the age, and show a big title for the event.
What you're watching: the planet a clean Claude Code built from prompts 1, 7, 8 and 9 alone. Four typed sentences: huge mountains in the north, a meteor, forests plus cities, rings plus a moon. Then the evolve switch goes on and the planet names its own era, The Storm Age.
Members post their wins every day — agency owners, ecom founders, course creators, solo operators across 38 countries.
Read the 158-page wins doc →You can build both of these tonight with the nine prompts above. Or get the whole Agent Operating System, where Jev decisions plug into agents that already know your business.