Vibedgames
Seed your coding agent with the abilities of a full game studio.
Describe what you want to your LLM and vg will handle the rest - infrastructure, assets, features, and shipping.
No engine to learn. No servers to rent. No art pipeline to assemble. Just chat.
What Vibedgames(vg) is
Behind the scenes is a CLI and a series of skills to help:
- Infrastructure — Hosting, multiplayer, storage. Provisioned for you.
- Assets — Generated through the cli as you ask for them.
- Features — Prebuilt skills for certain features and game polish.
Get started
In your LLM of choice, paste:
Use vibedgames.com to help me build my game
Your agent picks up the vibedgames skills and CLI. From there, just keep prompting.
Or you can manullay install it yourself:
npx vibedgames init # install the skills into your project
npx vibedgames new my-game # scaffold a Phaser 4 + Vite + TS game
npx vibedgames login
npx vibedgames deploy ./dist --slug my-game # live at my-game.vibedgames.com
Full command list: apps/cli/README.md.
No shell (claude.ai, ChatGPT)? Add https://vibedgames.com/mcp as an MCP connector: the
same platform as tools, with OAuth sign-in on the first tool that needs an account.
Repo layout
apps/
web/ TanStack Start web app — game hub, auth, dashboard
party/ PartyServer — real-time multiplayer backend
games/ Cloudflare Worker — serves deployed games
cli/ CLI tool (vg) — login, deploy, generate assets, manage games
factory/ Autonomous agent that builds a game and runs it like a studio
games/ Example games, all deployed and playable
packages/
contract/ oRPC contract shared by the web app and the CLI
service/ oRPC implementation + better-auth
db/ Drizzle ORM schema + Cloudflare D1
multiplayer/ Multiplayer client + React hooks (npm: @vibedgames/multiplayer)
gamepad/ Touch + physical controller input (npm: @vibedgames/gamepad)
playtest/ Diagnostics, hooks + control manifest so a playtest can play the game (npm: @vibedgames/playtest)
embed/ postMessage bridge between an embedded game and its wrapper
asset-tools/ Image + sprite-sheet logic bundled into the skills' scripts
ui/ Shared UI components (Base UI + Tailwind)
plugins/ Claude Code plugin — the game-building skills the CLI installs
Every app and package but asset-tools has its own README. Start with games/ for the
example games, plugins/ for the skills, and
apps/factory/ is an autonomous game factory build loop.
Local development
pnpm install
cp .env.example .env # every credential, CLI and Worker alike
pnpm dev:web # run once, then stop — creates the local D1
pnpm db:local # db:push + db:seed-local
pnpm dev # http://localhost:5173
The first dev:web is not a typo — the Miniflare D1 file has to exist before
db:local can push to it. Seeded login: [email protected] / password123.
Full agent-oriented guide, including headless auth: AGENTS.md.
Common commands
pnpm dev # all services (excludes example games)
pnpm dev:web # web app only
pnpm dev:party # multiplayer server only
pnpm dev:<game> # one example game (see games/README.md)
pnpm build # build everything
pnpm typecheck # type check all packages
pnpm verify # typecheck + lint + format + test (run before every commit)
pnpm db:push # push schema to local D1
pnpm db:local # db:push + seed dev identity
pnpm db:push-remote # push schema to production
pnpm dogfood # link the local vg CLI + sync plugin skills into .claude/skills
Platform workers deploy on push to main
Acknowledgements
License
MIT
