Browse hundreds of ready-made skills for Claude, Cursor, and more.
How to Prototype a 3D Game in a Weekend: The Friday-to-Sunday Workflow
You can ship a playable 3D game prototype to itch.io between Friday night and Sunday evening. Game jams have proven this for over twenty years. AI skills now compress the workflow even further: Friday is concept and scope, Saturday is build, Sunday is polish and ship. No engine bloat, no team, no months-long roadmap.
This is not a pep talk. Ludum Dare runs every four months and consistently ships 2,000 - 3,000 finished games in 48 - 72 hours. The format works because constraint forces shipping. AI skills give you the same constraint with a faster ramp - the boilerplate, asset stubs, and gameplay loop come pre-built so the weekend goes to the parts that actually feel like a game.
This guide is for indie devs, design students, and hobbyists who want one playable thing by Sunday night. We cover the 48-hour build anatomy, five AI game prototyping skills on Vibe Skills, and the Friday-to-Sunday workflow that fits in a weekend.
Browse hundreds of ready-made skills for Claude, Cursor, and more.
Why Weekends Are Enough Time to Ship a Playable Prototype
Game jams have proven the 48-hour build for two decades. Ludum Dare started in 2002 and now runs three times a year with 2,000+ entries per round. GMTK Game Jam pulls 8,000+ submissions in a single weekend. itch.io hosts thousands of jam pages every year, and most jam games ship in 48 - 72 hours from a cold start.
The format works because of three forcing functions:
- Scope is set before code starts. Jam themes prevent feature creep.
- Public submission deadline. Friday-to-Sunday means there is no "I'll polish it next week".
- Browser-first delivery. itch.io and Newgrounds ship to a browser link, not an installer.
What changed in 2026 is the ramp. AI skills cut the boilerplate that used to eat 8 - 10 hours of a jam:
- Three.js scene setup, lighting, camera rigging
- Player controller (keyboard, mouse, gamepad)
- Physics (raycast, colliders, basic AABB)
- Asset placeholders (low-poly character, environment props, skybox)
- Build pipeline that exports a playable HTML build
That setup work is now a 30-minute step. The rest of the weekend is design, level building, and feel.
Browse hundreds of ready-made skills for Claude, Cursor, and more.
The 48-Hour Build Anatomy
Every weekend prototype that ships follows roughly the same four phases. Skip a phase and the build doesn't make it to itch.io. Spend too long on one phase and the polish phase gets eaten.
| Phase | Time block | What you do | What you ship by end of phase |
|---|---|---|---|
| Phase 1: Scope | Friday 6pm - 10pm | Pick genre, write 1-page design doc, decide core loop, pick AI skill | Design doc + chosen skill |
| Phase 2: Build | Saturday 9am - 8pm | Generate boilerplate, build core mechanic, add 1 - 2 levels, wire input | Playable build with a win/lose state |
| Phase 3: Polish | Sunday 10am - 4pm | Sound, juice, tutorial popup, balance, bug pass | Build that doesn't break in the first 60 seconds |
| Phase 4: Ship | Sunday 4pm - 8pm | Export, write itch.io page, record GIF, post to socials | Public itch.io page with a working web build |
The four-phase structure leaves margin for the things that always go wrong: a broken physics edge case, a cursed asset import, a build that runs locally but breaks in WebGL. Plan for the bugs.
What "Vibe Coding" a Game Actually Looks Like
"Vibe coding" is the workflow of building software by describing what you want and letting AI generate the code, then iterating on the output. For games it works because most of the codebase is plumbing. The fun parts - feel, level design, sound, art direction - stay human, but the boilerplate is generated.
A vibe-coded weekend game looks like this: you write the design doc in plain English in a Cursor or Claude tab, install a Vibe Skills 3D game skill that ships with Three.js scaffolding, ask the AI to add the genre-specific mechanic, then hand-tune the feel - jump height, camera lag, particle intensity. The AI does the typing. You do the design. That split is what makes a weekend prototype possible for someone who is not a senior engineer.
5 AI Game Prototyping Skills on Vibe Skills
These skills are built to compress the boilerplate phase of a weekend prototype. All of them are in the 3D Games category on Vibe Skills and ship with Three.js scaffolding, a working build pipeline, and an itch.io-ready export.
1. Three.js Game Scaffolder
The starting point for almost every weekend 3D prototype. Generates a Three.js scene with a player controller, third-person camera, basic lighting, a skybox, and a ground plane with collisions. Output is a Vite project you can pnpm dev in 30 seconds and a pnpm build that produces an itch.io-ready HTML bundle.
Best for: any genre except pure 2D. Use this as your day-zero project.
2. First-Person Walker Skill
Generates a polished first-person controller (WASD + mouse look + gravity + sprint + jump) with footstep audio hooks and head-bob. Drop your own level mesh on top and you have a walking sim, horror prototype, or museum game by Saturday lunch.
Best for: walking sims, horror, exploration prototypes, narrative games.
3. Top-Down Arena Shooter Kit
Generates a top-down camera, twin-stick controller (keyboard or gamepad), wave spawner, basic enemy AI, projectile system, and a scoring HUD. The shooter loop is a known-good gameplay foundation - swap out the art and the spawn pattern and you have a brand new game.
Best for: arcade shooters, bullet hell, twin-stick action.
4. 3D Puzzle Platformer Skeleton
Generates a third-person platformer controller (variable jump, coyote time, ledge detection), a checkpoint system, and a level template with three stub levels you can edit in Blender or directly in code. Includes a death/respawn loop and a level-complete trigger.
Best for: puzzle platformers, parkour prototypes, speedrun-friendly indies.
5. Browser Driving Sandbox
Generates an arcade driving feel (acceleration curve, drift physics, camera lag, basic terrain) plus a low-poly car you can recolor in 10 seconds. Drop a track mesh and you have a racing prototype by Saturday dinner.
Best for: arcade racing, off-road driving, traffic sims, car-feel testing.
Browse all 3D game skills on Vibe Skills →
The Friday-to-Sunday Workflow
This is the exact schedule that fits a weekend. Adjust the start time but keep the phase order.
Friday 6pm - 10pm: Scope and Setup
Step 1: Pick a Vibe Skills game prototyping skill. Browse the 3D Games category and pick the skill that matches the genre you want to build. If you don't know yet, default to the Three.js Game Scaffolder - it adapts to anything.
Step 2: Write a one-page design doc. Open a new doc and answer these five questions in plain English. Do not skip any of them.
- What is the player doing every 5 seconds? (the core loop)
- What is the win condition? What is the lose condition?
- How many levels or how long is one run?
- What is the visual hook? (lighting, color palette, style reference)
- What is the one feature that makes this game memorable in 30 seconds of play?
Step 3: Install the skill and run the boilerplate. Get a working build running locally. You should see a player character moving in a Three.js scene before midnight. If you don't, drop scope - swap genres, simplify the camera, or pick a smaller skill.
Saturday 9am - 1pm: Build the Core Mechanic
Step 4: Replace the placeholder mechanic with your one feature. This is the only feature that matters. If your game is "first-person fishing in a haunted lake", today's morning is just fishing-cast logic and water shader feel. Nothing else.
Step 5: Get the win/lose state working. A 60-second prototype with a win screen feels like a game. A 60-minute prototype with no end state feels like a tech demo. Always ship the end state first.
Saturday 1pm - 8pm: Add Content and Levels
Step 6: Build one fully playable level or run. Not three half-baked levels - one polished one. Use placeholder cubes for geometry. Use the skill's placeholder character. Tune the feel.
Step 7: Add a tutorial popup. A two-sentence "WASD to move, click to fish" overlay on first launch saves your itch.io page from confused players who give up in 8 seconds.
Sunday 10am - 4pm: Polish
Step 8: Add sound. Even three sounds (footstep, ambient loop, win sting) lift a prototype dramatically. Free sources: freesound.org, opengameart.org, the AI-generated foley apps on inference.sh.
Step 9: Add juice. Particle on hit, screen shake on impact, a number popup on score. Juice is what makes a 48-hour prototype look like a 6-month one in a GIF.
Step 10: Bug pass. Play your build five times in a row. Fix anything that breaks twice. Ignore anything that breaks once.
Sunday 4pm - 8pm: Ship
Step 11: Build the production bundle. pnpm build in your skill's project. Test the production build in a fresh browser tab.
Step 12: Create an itch.io page. Title, one-line tagline, three screenshots, one GIF, controls, credits, your devlog link. The whole page should take 45 minutes if you have the assets ready.
Step 13: Post the link. Twitter, Bluesky, your dev community Discord, the relevant subreddit. Use the GIF as the preview, not the screenshot. Devlog posts that include the AI skill name (and a link to it) tend to get more clicks.
What to Do When You Hit the Saturday Wall
Most weekend prototypes die on Saturday afternoon. The mechanic is harder than it looked, the physics are weird, and you start questioning whether the game is fun. This is the wall. Every jam dev hits it.
The three rescue moves:
- Cut a feature. If the boss fight is fighting you, cut the boss. If the multiplayer is broken, ship single-player. The shipped prototype always beats the unfinished ambitious one.
- Swap to placeholder art. If you are spending Saturday in Blender, stop. Use cubes and capsules. Polish wins prototypes; assets win post-jam updates.
- Re-read the design doc. What was the one feature that mattered? Spend the rest of Saturday only on that.
The skill's placeholder assets are good enough to ship. Players will judge feel, juice, and the loop. They will not judge the rock prop in the background.
Where to Host and How to Share
itch.io is the default for browser game prototypes, full stop. Free hosting, no review queue, embeds work everywhere, and the audience expects raw weekend builds. Newgrounds is a good secondary post if your game has a comedy or arcade angle.
For visibility:
- Submit to a real game jam if your weekend overlaps one (Ludum Dare, GMTK, js13k for size-constrained builds, GitHub Game Off in November). Even outside an official jam, posting on a jam-themed page gets eyeballs.
- Cross-post a 15-second GIF to Twitter, Bluesky, and r/IndieDev / r/IndieGaming with the itch.io link.
- Add a devlog post to your itch.io page - one paragraph on what AI skill you used and what changed during the weekend.
The first 100 plays usually come from your own social accounts and one well-tagged Reddit post. After that, itch.io's "New" and "Popular" pages take over.
Frequently Asked Questions
Can I really build a 3D game in 48 hours with no game dev experience?
Yes for a prototype, no for a polished game. A weekend gets you a single playable mechanic with a win/lose state, one level, and an itch.io page. That is enough to validate the idea, build a portfolio piece, and decide if it deserves a longer build. AI skills on Vibe Skills handle the boilerplate so the weekend goes to design, not setup.
Should I solo or build with a team for a weekend prototype?
Solo for your first one. Team for your second. Solo prototypes ship more often because there is no coordination cost. Once you know your own pace, a team of 2 (one design + code, one art + sound) is the sweet spot for a weekend. Teams of 4+ usually don't ship in 48 hours.
Do I need to know Three.js or a game engine before starting?
You need to know enough JavaScript to read what the AI generates and tune values. You do not need to write Three.js from scratch. The Vibe Skills 3D game prototyping skills generate the engine setup; you write the gameplay. If you can edit React or vanilla JS, you can ship a Three.js prototype in a weekend.
How do I monetize a weekend prototype?
You usually don't. The first prototype is for portfolio, validation, and learning. Once a prototype gets traction (10k+ plays on itch.io is a good signal), the typical monetization paths are: pay-what-you-want on itch, a Steam Early Access build, or an ad-supported web release on portals like CrazyGames. For weekend builds, focus on shipping and devlog content - revenue is a month-3 problem.
What if my game crashes when I push it to itch.io?
Test the production build before you upload. Most weekend prototypes break in production because of asset paths or WebGL context settings - both fixable in 5 minutes if you catch them locally. The build pipeline that ships with skills on Vibe Skills is configured for itch.io's HTML5 hosting out of the box, which removes most of these issues.
Can I sell or modify the code from a Vibe Skills game skill?
Yes. Skills on Vibe Skills ship with a commercial-friendly license that lets you ship the code in your own released game on itch.io, Steam, or anywhere else. Creators keep IP of their skill; you keep IP of your game built on top of it.
Ship the Prototype This Weekend
The biggest reason weekend prototypes don't ship is not skill or engine choice. It is the Friday night where you "research a bit more" and never start. The next free weekend you have, follow the four-phase plan: scope Friday, build Saturday morning, content Saturday afternoon, polish and ship Sunday. Use a 3D game prototyping skill so the boilerplate is done before you make coffee on Saturday.
The portfolio of your first ten weekend prototypes is worth more than your hypothetical six-month dream game. Ship the small ones first.
Browse 3D game prototyping skills on Vibe Skills →
Skip the Three.js boilerplate marathon. Install a 3D game prototyping skill on Vibe Skills and ship a playable build by Sunday night.