Vibe Code Games With Cursor

Fork the Vibe Jam Starter Pack (or any working repo)

Cursor's strength is editing patterns that already work. Don't make it invent them from nothing — start with a project where the player moves around a scene, then change one thing.

Select the files, name the visible goal

Highlight what should change. Tell Cursor the one behaviour you want different in the running game. 'Slow the jump arc and add a landing thump on PlayerController.ts and audio.ts' is a Cursor prompt.

Play first, refactor later

Don't let Cursor reorganise the project until the loop feels right. The order is: working game → feel → cleanup. Swap that order and you'll lose a Saturday to a refactor that was never the actual problem.

Starter pack

Vibe Jam Starter Pack

A public starter pack with battle-tested agent skills, starter projects across 2D and 3D, and workflow references. It is the fastest route from Cursor prompts to a playable repo.

• Cursor
• Starter projects
• 2D + 3D

Agent skill

phaser-gamedev

A useful Cursor companion when editing 2D browser games because it keeps generated changes aligned with Phaser scenes, sprites, physics, input, and animation patterns.

• Cursor
• Phaser
• Fast edits

Agent skill

gamedev-assets

An asset-pipeline skill for validating manifests, probing sprite sheets, checking PNG dimensions, and debugging tilemap or tileset problems when visual changes break.

• Assets
• Spritesheets
• Debugging

Stay in the selection

Edit only the selected files unless a dependency forces you out. Match the existing patterns — don't reorganise the repo. Make the smallest playable change. If you spot a refactor that would help, list it separately at the end instead of doing it now.

Cursor's sweet spot is the visible diff

Feature passes you can see in the game within a minute. Asset wiring. Hitbox tuning. Small refactors where you can inspect the change at a glance. That's where Cursor is faster than anything else.

Tell it not to reorganise the repo

Cursor will happily 'improve' your project structure on every prompt. For games, that's a leak — every reorganisation breaks save paths, scene loaders, and the muscle memory you'd just built. Pin the structure and let Cursor work inside it.

Skills and starter repos are the rails

Without context, Cursor hallucinates Phaser APIs that don't exist or Three.js patterns from three versions ago. With a skill file loaded and a working starter open, it stays inside the lines.

Is Cursor a good place to start if I've never built a game?

Yes, on a project that already runs. Cursor on a blank repo is brutal — you'll spend half the time arguing about scene setup. Cursor on the Vibe Jam Starter Pack, where a player is already moving around, is the fastest way I know to feel the loop click for the first time.

How is Cursor for games different from Cursor for web apps?

Web apps need correct code. Games need correct code that feels right when you play it. Cursor handles the first. The second is on you — and the workflow change is that you should be playing after every edit, not after every five.

Will these workflows still work if I switch to Claude Code?

Yes. The starter repos, skill files, and prompt patterns use the open Agent.md convention — Claude Code reads them too. I move between Cursor and Claude Code constantly: Cursor when I want speed, Claude when I want depth.