Looking for ideas first? Browse Awesome 3D Prompts and Awesome Opus 5.5 Prompts.
One prompt. An empty folder. A 3D game you can share.
Paste one prompt into your coding agent. It designs a small browser game with you, builds a playable greybox, lists the 3D models it needs, and swaps in the models you make in Tripo Studio. You never write code; you play, give feedback and make the models.
1 prompt · 6 stages · 4 example games · 0 human interventions in all four builds
Start here · The prompt · Example games · Get the models · Discussions · Changelog · Tripo Studio ↗
Star this repository to find it again. To hear about new prompt versions and example games, choose Watch → Custom → Releases.
- Copy the prompt. Open an empty folder in your coding agent (Claude Code, Codex, Cursor, …) and paste the prompt.
- Answer, then play the greybox. The agent asks up to five questions, writes a one-page design and builds the game from simple shapes. Play it and say what feels wrong; it fixes and retests.
- Make the models, then swap them in. The agent writes
assets.jsonand Tripo Studio steps for every model. Generate them, export GLB, and the agent puts them in the game and checks each one against its greybox.
Want to see the result before you start? Clone this repository and run any example game.
Version 1.0 · 2026-09-29 · about 2,600 words. Copy the block below (the copy button is at its top right), or read it in prompt/vibe-gaming.md.
Show the prompt
Help me make a small 3D browser game, step by step. I have never made a game before.
Before you write any code, ask me up to 5 short questions in one message: what the game is about, the one thing the player does, keyboard or phone or both, the art style, and anything I already have. Wait for my answers.
Then work in stages. Stop at the end of every stage, tell me how to try it, and wait for my feedback:
1. Design — write GDD.md, one page: core loop, controls (keyboard and touch), win and lose, camera, and a table of every object on screen with an id, its size in metres and which way it faces. Keep it to one level and one core loop. Make up your own characters, names and level layout; do not copy any existing game, and do not make anything look like a well-known game character or item either. For every character that animates, list its states (for example idle, run, attack, hurt, knocked down) and when it switches between them, and say whether it is a person or another kind of body (an animal, a robot dog, a bug); only people get bones, so a body that is not a person is built from parts that move in code. If characters fight, write for each attack: which animation it uses, how much damage it does, and at what fraction of the animation the hit lands and ends. If a machine or object has parts that move, can be shot off or break apart, list its parts: what each part does, where it hinges, how much it can take, and what changes when it breaks. If parts can be swapped between machines or characters, give all of them the same set of slots, and for each slot write one attach point (where it sits, measured from the centre of the feet) and which way a part faces on that point.
2. Greybox — build it with Three.js and Vite, no game engine. Use only boxes, cylinders and capsules, sized from the table. Keep everything about how objects look in one place: a registry from id to a builder function, so a 3D model can replace any placeholder later without touching gameplay code. Build an object with parts as a group of named child placeholders, one per part, each turning around its own hinge, and let gameplay find parts by name. If parts can be swapped, hang each swappable part on a named attach point; swapping a part means hanging another part on that point and scaling it to fit the slot, and gameplay still finds parts by name. Every placeholder faces +Z. If the player jumps, make it feel good: a jump pressed just before landing still counts, a jump just after walking off a ledge still works, and holding the button jumps higher. If the player fights, make it feel good: a button pressed during an attack queues the next one, a hit freezes both fighters for a split second and pushes the target back, a character that was just hit cannot be hit again at once, and enemies take turns attacking instead of all at once. Show states on the placeholders (a colour or a lean) so I can see them. Moving characters must look smooth on both 60 Hz and 120 Hz screens. Done when I can play a full round and restart, on desktop and on a phone. If a later change adds a new state, add it to GDD.md and tell me which animation it needs.
3. Asset list — write assets.json with one entry per id: its kind (prop, person or parts), size in metres (height for people, longest edge for everything else), a polygon budget in triangles (at least 500), and one English image prompt. Give every prompt the same art-style sentence, describe the shape and proportions it must have to fit its size, and end it with "single isolated object, centered, on a plain white background". At most 8 entries; if several enemies share a shape, they share one entry, and one that differs only in colour gets a one-line texture prompt on that entry instead of a new entry.
- A person that animates must stand in a T-pose, facing the camera, with its head no more than a third of its height, arms long enough to reach mid-thigh, a body no wider than its shoulders, space between the arms, legs and body, and nothing loose that would flap or stick out (scarves, long hair, bandana tails, capes). Give it a list of animations taken only from these names in the Tripo library: idle, walk, run, jump, jump_down, fall, box_01, box_02, box_03, front_kick_01, slash, shoot, hit_to_body_01, hit_to_head, defeat_02, cheer. The name is only a label, so pick by what the motion is: jump has a long crouch before take-off, jump_down is a drop through the air, fall is tripping over onto the ground, defeat_02 is being knocked down, and the attacks are much slower than a game needs.
If no name fits, write a one-line description of the motion instead, starting with its name and a colon (for example "dodge: a small character rolls forward and gets back up"); this works for people only. Anything that only spins, bobs, squashes or flashes is animated in code, not in Tripo.
- An object with parts (a machine, an animal or robot animal, anything that breaks apart) is one model that Tripo will split. List its parts in plain words (for example "left_cannon", "armour_plate", "front_left_leg"), at most 10, and if parts can be swapped, say which slot each part fits. Write the image prompt so that any central body is clearly its own piece, and every part in one main colour of its own, with a gap between parts. Parts that walk or swing are moved in code at their hinges, not rigged.
- If I want a second look for the game (for example a style switch, or an elite enemy), give the entry up to 2 styles from Mecha Pop, classic, Wood, or "own image: [one line describing the look]" if I will make my own style picture and upload it; or "none".
Add up the triangles and texture memory for the busiest moment on screen and say whether a phone can handle it; each Tripo model comes with only one colour texture at the chosen resolution (a split model shares it across its pieces) and no other maps.
4. My turn — write these steps once, exactly as written here; do not add or change steps, and do not try to generate the models yourself. Then give me one table with a row per entry: id, kind, prompt, polygon budget, file name, animations or parts, and style (or "none"):
a. In Tripo Studio (studio.tripo3d.ai), open Image, paste the prompt and generate. Pick the image whose shape best matches the list.
b. Hover over that image and click Generate 3D. It may open on the HD Model tab, so click the Smart Mesh tab and choose P2.0 (P1.0 if P2.0 is not on your plan), open Topology and check it says Triangle (not Quad) and Polycount = the budget every time, because it resets even though it says it saves your settings; Number of Generation 1. Generate. (For a soft, rounded person such as clay or plush, the HD Model tab with H3.1 can look better; everything else stays the same.) Parts only: do not use Smart Mesh; use the HD Model tab instead: pick H3.1, turn on Generate in Parts, choose Simple, open Geometry & Texture and set Topology to Triangle and Polycount = the budget. Every model: before you click Generate, change Privacy to Private (it starts as Sharing Only).
c. Parts only: you will get several pieces, named tripo_part_N, not always one per part on the list. Open Fill Parts, choose AI Completion and click Part Completion to fill the gaps; the result is saved by itself.
d. Open Texture, make sure Texture Resolution is 2K (it starts at 8K, then remembers your choice), and Generate Texture. If the entry has styles, export this default version first (step f; for a person, do step e first), then do this once for each style: pick it under Create Your Own Texture Style, Generate Texture again, and export it as the id plus the style name (for example robot_mechapop). To go back to no style, click the chosen style again in the style window. For a person, a new texture removes its animations: apply them again in Animate (this costs no credits) before you export. For an "own image" style: in Image, make a picture from its line, download it, and upload it under Create Your Own Texture Style.
e. People only: open Rig, choose Humanoid and the Mixamo skeleton, click Auto Rig. Then open Animate, make sure All is selected, search each animation name from the list and click it to apply; wait until it finishes Retargeting before you click the next one. For a line that is a description, paste it into Text to Motion and generate (this one costs credits).
f. Click Export: GLB, texture resolution 2k, file name = the id. For people, make sure Export Skeleton is on, click Number of Animations and choose Select All (it starts at 0, which exports no animations), then make sure Animation stay in Place is on. If you see Pack UV, make sure it is off.
g. Put the files in public/assets/, replacing any old file with the same name.
Wait until I say they are in.
5. Swap — load each GLB in place of its placeholder: scale it to the size in the list (people by height), sit it on the ground, and add an environment map so materials are not black. Render every model next to its placeholder and check it faces the same way; rotate it if it does not. First list what is really inside each file: animation names (Tripo often renames them: defeat_02 can come out as defeat_03, and a Text to Motion clip is named after the start of its description) and, for split models, every piece with its name, size and position. Match animations by the closest name. Match pieces by name first; pieces still called tripo_part_N belong to the part whose placeholder they overlap most, so group them in code. The sizes stored in the file are not reliable, so recompute each bounding box before you measure anything. The order of meshes changes from file to file, so always match pieces by node name. Tell me what you matched and what is missing. Every piece keeps the whole model's origin: move each part's pivot to its hinge before you turn it, and since a few pieces may still have small holes, make sure nothing looks see-through when a part comes off (close it, show both sides, or put something dark behind it). Each piece has its own material, so merge the pieces of one part into one mesh if the draw calls hurt on a phone. If parts can be swapped between machines, line up where each part joins with its slot's attach point and scale it to fit the slot. When a swapped part has a different height, such as another machine's legs, seat everything above it on the new part's real height and hinges, not the old part's or the placeholder's, so nothing floats or sinks. If an entry has style versions, they have exactly the same shape and UV, only the textures differ: load the shape once from the default file, take only the textures from each style file, and add a button that switches skins by replacing the textures on the materials. Never pair the shape data of one file with another file.
Look at the frames of every animation before you use it: pick the part you need, find the moment a punch or kick really lands, and check arms and feet do not go through the body or clothes. Tripo animations are the same for every body shape, so on a character with a big head, a round belly or thick clothes the arms often sink into the hips or chest when they hang down and pass through the head when they go up. Measure this in code instead of judging it from small frames: in every frame of every animation, work out where the arm vertices really are and test whether they are inside the rest of the body (a winding-number test stays right on clothes and open meshes), using the T-pose as zero. Also look at close-ups from the front and from a 3/4 angle, including the armpits. If an arm goes in, fix it in code: after each animation frame, turn the upper arm outward at the shoulder just enough to clear the body (hips, belly, chest and head). Tell me the worst depth for every animation before and after the fix.
Play character animations by name with an AnimationMixer, blending between states, and keep the character in place so only gameplay code moves it: "stay in place" can still leave the body ahead of or behind its feet, so check the hips over the whole clip and centre them. Match walk and run playback speed to how fast the character really moves so the feet do not slide. If a character must do two things at once (run and shoot), play the legs from one animation and the upper body from another: the legs always face where it runs, the upper body twists toward the aim, and it backpedals when aiming behind. When one model is used by several characters at once, clone it with SkeletonUtils so each has its own skeleton. Check where characters stop and touch things using the models' real sizes, not the placeholders', and measure every frame of a crash or knockdown so no character ends up inside what it hit. On a phone held upright, measure how much of the screen height the player takes up and how much of the screen is empty sky or background, and tell me both numbers. Keep a button that switches between greybox and models. The colour tints and white hit flashes that showed states on the placeholders wash out painted models, so on models glow only the part that matters and brighten its own colours instead of adding white; then check that a landed hit is still easy to see and hear (a flash or sparks at the spot, a jolt of the part, a sound). Effects that shake a part must not move the point used for hit detection. Do not change gameplay code; if timings, sizes or triggers need new numbers, tell me what and why, and wait for my yes. Tell me which files, animations or pieces did not load and why.
6. Publish — help me put it on a free static host and give me the link. Ask me before you create any account, repository or public page.
Test your own work before you hand it to me: run the build, open the game, check the console for errors, and tell me exactly what you checked. If the game has fights or levels, write a small bot that plays a full round and report what it hit and whether it won. Wait for every test to finish before you reply; never start a test with & or in the background. Use only a browser that is already installed on this machine; never download one. If you cannot test something, tell me what to try myself. If something does not work, say so.
The agent works in six stages and stops after each one for you:
| Stage | The agent | You |
|---|---|---|
| 1 Design | asks up to five questions, writes a one-page GDD.md |
answer, approve |
| 2 Greybox | builds the game from boxes, cylinders and capsules, and tests it with its own bot | play it, say what feels wrong |
| 3 Asset list | writes assets.json: every model, its size, triangle budget and generation prompt |
check it |
| 4 Your turn | writes step-by-step Tripo Studio instructions | make the models, export GLB |
| 5 Swap | loads your models and checks each one against its greybox | play it again |
| 6 Publish | helps you put it on a free static host, and asks before creating any account or public page | get the link |
Why each line of the prompt is there, and what every draft added: prompt/CHANGELOG.md.
Each game was built from an empty folder with a version of this prompt, by Claude Code with claude-opus-5-5. The source is in examples/; the Tripo models are not included, so a fresh clone runs in greybox.
 Snowdrift Dash Endless downhill skiing · prompt v3.2 Play ↗ · Source |
 LANTERN ALLEY 3D arcade beat 'em up · prompt v2 Play ↗ · Source |
 PIT NINE Top-down arena shooter · prompt v3 Play ↗ · Source |
 TOY BOX BOUT 1v1 part-swapping robot battler · prompt v3.1 Source (not hosted yet) |
A human intervention means giving the agent an implementation hint or fixing something for it. Saying "go", reporting what you see while playing, and choosing between options the agent offered do not count.
Claude Code · claude-opus-5-5 · prompt v3.2 · 8 models · 0 human interventions
| Greybox | With Tripo models |
|---|---|
 |
 |
Steer a skier down an endless slope; it speeds up the longer you last, and one hit ends the run. The skier is rigged, with two library animations and a gliding motion made with Text to Motion. Play ↗ · Source
Claude Code · claude-opus-5-5 · prompt v2 · 10 models, 6 rigged characters · 0 human interventions
| Greybox | With Tripo models |
|---|---|
 |
 |
A comic-book hero clears an alley of four waves of thugs and their boss, with punch combos, kicks and running attacks. When exported animations came back renamed and several times slower than the greybox timing, the agent found it, measured every frame, and proposed new timings before changing anything. Play ↗ · Source
Claude Code · claude-opus-5-5 · prompt v3 · 8 models, each in two styles · 0 human interventions
| Greybox | With Tripo models |
|---|---|
 |
 |
Fight robot hounds, then shoot a giant machine apart: every broken part takes away one of its attacks. The hounds and the boss are split into parts in Tripo and moved in code, and one button switches the whole game to a second texture style. Play ↗ · Source
Claude Code · claude-opus-5-5 · prompt v3.1 · 8 models, robots in three paints · 0 human interventions
| Greybox | With Tripo models |
|---|---|
 |
 |
Plastic toy robots fight one on one inside a toy box. Break the rival's head to win, take one of its parts and fit it to your robot. Every robot is generated in parts, and each part fits any robot's matching slot. Japanese text with an English toggle. Source
Run any example:
git clone https://github.com/TripoGrowthLab/vibe-gaming-interactive-handbook.git
cd vibe-gaming-interactive-handbook/examples/ski
npm install && npm run devEvery example lists its models in assets.json, with the size, triangle budget and the exact prompt used. Generate each one in Tripo Studio, export GLB, name the file after its id and put it in that example's public/assets/. Reload the page: whatever you added replaces its greybox, and anything missing stays greybox. Each example's README has the details.
The Tripo models themselves are not in this repository; your generations will differ a little from ours, which is why stage 5 has the agent check every model against its greybox.
Made something with the prompt? Share it with a link and a screenshot. Found a step where the agent or Tripo Studio did not do what the prompt says? Report it; every line in the prompt came from a report like that. See contributing.
- Tripo Studio: every 3D model in the example games
- Claude Code with
claude-opus-5-5: the coding agent that built all four games from the prompt - three.js: rendering, animation and model loading
- Vite: dev server and build
- Playwright: the agent's own play-tests and screenshots, in each example's
tools/ - glTF Transform: model checks in LANTERN ALLEY
Curated by TripoGrowthLab. The cover is AI-generated conceptual artwork; the game screenshots are real captures of the examples. The MIT license covers the prompt, the example code and our documentation; it does not cover Tripo trademarks or models you generate. See rights.