Vibe code game development
Vibe Code Game Development
You don't need a studio or years of engine experience. You need a small idea, the patience to test it, and a stack of skills that lets the AI carry the implementation.
Before AI tools, becoming a game developer meant picking up code, art, animation, sound, and engine tooling — usually all at once. The thing that ate me alive when I first tried was the gap between watching a tutorial and starting my own project. AI closed that gap. I've shipped 77 build videos and a Discord of 100+ game builders since, mostly by leaning on this workflow.
What hasn't changed: you still need taste. Someone has to decide what the game is, what feels right, and what to fix next. The pack handles the technical side — the SKILL.md files the agent loads, the source code for every game in the showcase, the prompts I actually used — so you can spend your energy on direction instead of staring at a blank file.
Why It Matters
- A real path from 'never built a game' to playable build — the Pirate Beat 'Em Up tutorial walks the whole thing in 17 prompts
- Skills that turn Claude Code, Codex, or Cursor into a game-dev teammate instead of a generic assistant
- Source code for every game in the showcase — fork it, change one thing, see what happens
Workflow
Be the director, not the engineer
Pick the genre, the camera, the one verb the player can do, and what the first playable minute proves. You're not writing implementation. The agent does that. You're writing the brief.
Let the skills do the engine work
phaser-gamedev for 2D. threejs-builder for 3D. love2d-gamedev for iOS. The skill file is what makes Claude Code or Codex behave like a teammate who has actually shipped a game — instead of one who's only built React apps.
Play after every change — every time
If you can't tell what changed by playing the build, the change was too big. Smaller passes, more often. This one habit is what separates a 'cool demo' from something you finish.
Public Vault Excerpts
Agent skill
phaser-gamedev
A Phaser 3 workflow skill for scenes, sprites, Arcade and Matter physics, tilemaps, animation, input, and game architecture. Use it when a browser game needs real game-loop structure instead of generic React-style code.
- Phaser
- 2D
- Browser games
Agent skill
threejs-builder
A Three.js skill for scene setup, camera and renderer wiring, lighting, geometry, materials, animation loops, GLTF loading, responsive rendering, and performance guardrails.
- Three.js
- 3D
- WebGL
Project
Castle Clash Duel
A public Phaser 3 tactical strategy game using Tiny Swords pixel art. The useful lesson is not only the source code: it is the turn-based combat loop, sprite animation handling, and AI-assisted iteration pattern behind the build.
- Phaser
- Strategy
- Pixel art
Project
Forest Census
A public Three.js mini-game built with Codex CLI and the threejs-builder skill. It is a compact example of a single-scene game that can be hosted statically and improved in small AI-assisted passes.
- Codex
- Three.js
- Mini-game
Agent skill
retro-diffusion
A pixel-art generation workflow for spritesheets, img2img edits, walk cycles, idle loops, attack sheets, and animation consistency from reference images.
- Pixel art
- Spritesheets
- Animation
Agent skill
animated-spritesheets
A workflow for turning a single character reference into an animated spritesheet through frame recovery, background cleanup, normalization, contact sheets, and GIF previews.
- Characters
- Motion
- Pipeline
Playbook
The Full AI Sprite Pipeline
A public-facing playbook path from image generation to video reference to a Phaser test harness, showing how game-ready character sprites come from a repeatable pipeline rather than one lucky prompt.
- GPT Image
- Sora
- Phaser
Prompt Patterns
Get to a playable loop before anything else
Before adding levels, content, or art, get one playable minute working. Movement, one interaction, one way to win or lose. Use the existing engine conventions in this repo — don't reinvent scene structure. Add a small debug overlay for anything I'll need to tune (speeds, hitboxes, spawn rates).
One system per pass
Change only one system. Tell me: what the current behaviour is, what we're aiming for, which files you expect to touch, and how I can see the difference in the running game. If you find yourself wanting to touch a second system, stop and ask first.
Frequently Asked Questions
What does 'vibe coding games' actually mean in practice?
You describe what you want in natural language, the agent implements it, you play the result, and you steer the next change. The craft isn't typing — it's scoping, reviewing the running build, and naming what to fix. The agent does the keystrokes.
Can someone with zero coding experience really do this?
Yes, if you're willing to direct and test. AI removes most of the blank-page friction that used to stop people. What it doesn't remove is the part where you have to play your game, notice what's off, and describe it specifically. That's the work that's still yours. Everyone in the 100+ Discord started somewhere — most of them not as coders.
How is this different from the AI game development page?
This page is for people just figuring out whether they can start. The AI game development page goes deeper on the workflow itself. Same toolkit underneath — different angle of approach.