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

How to adjust sprite bounds and object properties by hand with Vibe Game

Use the web Dashboard to preview animations and tweak character settings without writing code.

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 non-programmer or designer who has a generated game and wants to fix how sprites and characters look and behave.

The problemSmall visual fixes like sprite bounds or animation timing usually require editing files or asking an agent for every change.

The outcomeYou adjust sprite bounds and character animation and properties in the Dashboard, then play the result in the Play tab.

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 init inside your game folder, then vibegame start
  5. Open the Dashboard, go to Assets to preview animations and adjust sprite bounds, then go to Objects to configure character animations and properties
  6. Open the Play tab to test the game after each change

Prompt for your agent

Using the VibeGame repo at https://github.com/tettethu/VibeGame, start a project with vibegame start and open the VibeGame Dashboard. Expected output is updated sprite bounds and object properties for <character name> in the Assets and Objects tabs. Verify by opening the Play tab and confirming the character's animation and size changed.

Caveat. The README describes the Dashboard tabs but does not give a dashboard address, so find it from the output of vibegame start.

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