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

How to continue polishing an existing Vibe Game project with Vibe Game

Point the agent team at a game you already built and direct its next round of edits.

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 already has a Vibe Game game folder and wants to keep improving one part of it, such as a boss fight.

The problemReturning to a generated game means reloading context and running the agent again from the right folder.

The outcomeThe agent team continues work on the named part of your existing project, and you can run or close the game from the CLI.

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. vibegame start --project ./my-game "Continue polishing the boss fight"
  5. vibegame run --port auto
  6. vibegame close when you are finished testing

Prompt for your agent

Using the VibeGame repo at https://github.com/tettethu/VibeGame, run vibegame start --project ./<project-folder> with the request "<change request>". Expected output is an updated game in <project-folder> with the requested change applied. Verify by running vibegame run --port auto and checking that the changed behavior appears in the browser.

Caveat. The README says the agent is launched from Vibe Game's managed session, so keep the checkout in place because pulling updates changes the installed CLI without reinstalling it.

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