DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a playable 2D web game from one prompt with Vibe Game

Install Vibe Game, describe a game in plain language, and get a playable 2D browser game.

  • Top pick
  • Games and hobbies
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code
  • Codex

Authorization notice. Vibe Game is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA hobbyist or indie developer with no game engine experience who wants a playable 2D browser game from a text idea.

The problemBuilding a 2D game normally means learning an engine, writing code, and wiring up assets before anything is playable.

The outcomeA new Vibe Game project in my-game that the agent team builds from your prompt, which you can run in the browser with vibegame run.

What you need first

  • Python 3.12 or newer
  • uv installed
  • tmux installed
  • Claude Code or Codex CLI installed and signed in
  • A terminal to run the setup and start commands

Steps

  1. git clone https://github.com/tettethu/VibeGame
  2. cd VibeGame
  3. ./setup.sh
  4. mkdir my-game && cd my-game
  5. vibegame init
  6. vibegame start then give the agent a prompt such as a compact roguelike dungeon with one boss encounter, then run vibegame run --port auto

Prompt for your agent

Using the VibeGame repo at https://github.com/tettethu/VibeGame, set it up with ./setup.sh, create a project in my-game with vibegame init, and start it with vibegame start using the prompt "<game idea>". The expected output is a playable 2D web game in my-game, launched with vibegame run --port auto. Verify that the run command prints a local address and the game loads in a browser.

Caveat. Claude Code agents launch with --dangerously-skip-permissions, so run the first-time consent step described in the README before starting, and only use this in a project folder you are willing to let the agent edit.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page