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

How to run the standard build workflow for a full game goal with Vibe Game

Give an agent one end-to-end game development goal using Vibe Game's standard build workflow.

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 developer who wants the agent to plan and build a complete small game from a single goal statement.

The problemWriting a full game brief and coordinating build steps by hand takes time before any playable result exists.

The outcomeYour agent runs the standard /vibegame-build workflow and produces a game matching your goal, which you can then run locally.

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. In your Claude Code or Codex session, enter /vibegame-build Build a compact roguelike dungeon with one boss encounter

Prompt for your agent

Using the VibeGame repo at https://github.com/tettethu/VibeGame, run the /vibegame-build workflow in my-game with the goal "<end-to-end game goal>". Expected output is a built game in my-game that matches the goal. Verify by running vibegame run --port auto and confirming the goal's main encounter is playable.

Caveat. The /vibegame-build command is shown in the README as a slash command for an agent session, so it runs inside Claude Code or Codex rather than the shell.

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