AI Vibe Coded Games

It usually means a game built by describing an idea to an AI coding tool, trying the generated code, and asking for changes. The label describes a process. It does not tell you whether the game is finished or good.

A maker writes a prompt describing the rules, controls, and look. The AI produces code. The maker runs it in a browser, tests what happens, and requests specific fixes. Our originals publish their opening prompts so you can see that starting point.

A coding assistant can draft browser game code from instructions. Our directory has pages for Claude, ChatGPT, Gemini, Grok, Cursor, and Codex. Some are chat assistants and some work inside a coding workspace. A tool name alone does not show how much help the maker needed.

Yes, a small game is a reasonable first project. Start with one action and one way to score. You still need to save files, open the game, describe bugs, and test changes. Learning a little HTML and JavaScript makes those steps easier.

The originals load in a browser iframe with limited permissions. That is not a security guarantee. External games run on other sites with their own policies. Avoid unexpected downloads and do not enter passwords or personal details just to try a game.

Use the Submit page for the information we need: a playable URL, creator credit, tool, genre, phone support, and a source link. Email intake is a placeholder during this preview, so submissions are not being received yet.

Each directory entry names the creator and links to their site and the source used for the listing. The play link goes to the creator's game. We do not copy or embed third-party games. The Credits page collects those attributions.

Generating code is only part of making a game. Difficulty, touch input, clear feedback, and reliable restarts take testing and revision. Small experiments may have uneven pacing or bugs. We show build notes when available rather than treating AI involvement as proof of polish.