Getting started
Learning paths through this topic
What Is Vibe Coding? Meaning and Plain Definition
Vibe coding means telling an AI what you want and judging the result by using it, without reading the code the AI wrote.
Make enemy turrets lead their shots so they hit a moving hero
A turret aimed straight at the hero always shoots behind a moving target, and the AI's first fix is to aim at where the hero will be after a guessed time. This entry finds the exact aim point, and says clearly when no shot can ever catch the target.
Make sure every picture and sound the game asks for really exists
The game runs on your computer, then shows empty boxes and silence once it is online, because a file name differs by one capital letter or a file was never added. This entry gives a check that lists what is missing, what only differs in spelling, and what nobody uses.
Fix a game that shows nothing once it sits in a folder on the web
A game can run perfectly on your computer and show a blank screen when put on a hosting page that serves it from a sub-address. The cause is how file paths are written. This entry finds the risky paths and rewrites them so they work wherever the game sits.
Decide which sounds to load at once and which to play as a stream
Shots, jumps and hits must play the instant you press the button, while a long music track must not be loaded whole. Get this split wrong and either the sound lags behind the action or the game eats memory. This entry gives the rule and the memory cost.
Record a run so you can show the AI exactly how the bug happened
"I fell through the floor somewhere in level three" is hard for an AI to fix, because it cannot press the keys. A tiny recording of which buttons were held in each step replays the same run again and again. This entry stores it compactly and refuses broken recordings.
Keep your platformer small enough to load on a phone before you publish
A game that works on your computer can still take minutes to open for a friend on a mobile connection, and the AI will happily keep adding pictures and sounds. This entry gives you a size limit to hand your AI and a check that names what to cut first.
Stop a reused bullet slot from being hit or removed by an old reference
To save effort, games reuse a fixed set of bullet slots. Then something holding on to a bullet that is long gone suddenly removes or moves a different, brand new bullet. This entry shows how to make such old references harmless and how to behave when all slots are taken.
Make the camera follow the hero without showing empty space past the level
A camera that sticks to the hero shows the grey void at the level's edges, and a camera that is clamped carelessly shakes when the level is smaller than the screen. This entry gives a follow that eases, stops at the edges and centres a small level.
Decide what a checkpoint brings back and what stays collected after a death
After a fall the hero reappears at the checkpoint, but are the coins back? The key found after it? The opened door? Left undecided, the AI mixes them up, and the score counts the same coin twice. This entry sorts the things into two kinds and gives each a clear rule.
Boil thousands of repeated error lines down to what you paste to the AI
When something breaks inside the game loop, the same error appears sixty times a second, and the one line that explains the cause scrolls away. Pasting all of it overwhelms the AI. This entry groups lines that differ only in numbers and shows each kind once with a count.
Stop fast shots and falling heroes from going straight through thin walls
A fast bullet can jump from one side of a thin wall to the other between two frames and never touch it. The AI checks only where the bullet is, not where it travelled. This entry shows how to test the whole path and where along it the hit happened.