菜单
Deploy browser games to vibedgames. Use when the user wants to deploy, publish, ship, or host a game — especially static HTML/JS games built with Vite, Phaser, Three.js, or plain HTML. Triggers on: 'deploy this game', 'publish my game', 'ship it', 'host this', 'put this online', 'make it playable'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use the `vg generate` CLI to search, inspect, run, and manage 1200+ generative model endpoints. Trigger when the user asks to "generate an image", "make a video", "search models", "run a model", "fetch schema", "check pricing", "upload an asset", "queue async job", "track request", or any direct interaction with the model endpoint catalog. This is the foundational skill. Every other media skill in this repo executes its work through `vg generate` commands. Use `--json` whenever the output will be parsed by an agent.
Build 3D browser apps AND games with Three.js (r150+, ES modules): scene setup, geometries, materials, lighting, animation, GLTF models, physics (Rapier/cannon-es/arcade), character controllers, follow/third-person cameras, fixed-timestep loops, post-processing, and performance/debugging. Use for 'create a three.js scene/app/showcase', any 3D web content, and turning a scene into a game — 'add physics to my three.js game', 'third-person/character controller', 'follow camera', 'jump and gravity', 'collide with / pick up objects', 'structure my 3d game'. Trigger: threejs, three.js, 3D scene, WebGL scene, GLTF/GLB, OrbitControls, Rapier, cannon-es, 3D game, third-person controller. For 2D games use `phaser`; for engine-agnostic feel/balance/level craft use the game-craft skills.
Turn a character anchor into an engine-loadable animated spritesheet by generating ONE labeled pose-board image (a grid of the same character in the frames of an action) and slicing it. Works for any action — idle, run, jump, attack, hurt, crouch, death, roll. Generates a per-frame-labeled pose board on a flat chroma matte, recovers/slices the frames, keys + despills, snaps to crisp native pixels, normalizes with headroom, and packs spritesheet.png + a manifest. Triggers: 'sprite animation', 'animated spritesheet', 'attack animation', 'walk/run cycle', 'animate this character', 'game sprite animation', 'sprite pose sheet'.
Interview the user relentlessly about the game they want to make until the idea is build-ready, resolving each branch of the design tree one question at a time. Use when the user has a fuzzy or one-line game idea and wants to flesh it out before building: 'grill me about my game', 'help me figure out what game to make', 'stress-test my game idea', 'interview me about the game', 'I want to make a game but I'm not sure what'. Not for when the user already knows what they want built — go straight to game-playbook.
Build and ship Three.js apps on Capacitor iOS with Vite and Swift Package Manager: GLTF loading, assets_index animation UI, OrbitControls mouse/touch mappings, and iOS sync/run troubleshooting.
Build 2D browser games with Phaser 4: scene lifecycle, sprites, Arcade/Matter physics, tilemaps, WebGL rendering, filters, lighting, shaders, DynamicTexture/RenderTexture, SpriteGPULayer, TilemapGPULayer, and Phaser 3 to 4 migration. Trigger: phaser, phaser 4, phaser v4, create phaser game, add phaser scene, phaser sprite, phaser physics, phaser tilemap, phaser arcade, phaser webgl renderer, phaser filters, phaser SpriteGPULayer, phaser TilemapGPULayer, migrate phaser 3 to 4.
| name | deploy |
| description | Deploy browser games to vibedgames. Use when the user wants to deploy, publish, ship, or host a game — especially static HTML/JS games built with Vite, Phaser, Three.js, or plain HTML. Triggers on: 'deploy this game', 'publish my game', 'ship it', 'host this', 'put this online', 'make it playable'. |
Deploy static browser games to {slug}.vibedgames.com using the vibedgames CLI.
vgnot on PATH? The global install fromvibedgames initis best-effort. If anyvg <cmd>below fails with "command not found", substitutenpx vibedgames <cmd>— it works identically.
If the user has no project yet, scaffold one in a single command. vg new pulls the official engine template (or a minimal inline starter) and drops a vibedgames.json in place so deploy works without further config:
vg new my-game # Phaser 4 + Vite + TS (official phaserjs template)
vg new my-game --engine threejs # Three.js + Vite + TS starter
vg new my-game --engine react-r3f # React + R3F + drei + Vite + TS starter
vg new my-game --engine none # minimal Vite + TS + canvas (offline; no engine)
vg new my-game --template foo/bar # any github degit spec
Pick the engine that matches the game the user described:
phaser (the default)threejsreact-r3fnoneAfter scaffold:
cd my-game
npm install
npm run dev # local preview
The matching skill (phaser, threejs, etc.) will load automatically in Claude Code based on the deps in package.json. Pass --here to scaffold into the current directory.
The game directory must contain an index.html at the root. Typically this is the dist/ output from a build tool (Vite, webpack, etc.).
Always check auth before building or deploying. whoami exits non-zero
when unauthenticated:
vg whoami
If it prints Not logged in (or similar) or exits with an error, run
login before anything else:
vg login
This auto-opens the user's browser to a device-code confirmation page
and prints an 8-character code in the terminal. Tell the user:
"I opened a browser — confirm code XXXXXXXX." Wait for the CLI to
print Logged in successfully before continuing. If the browser
didn't open (remote shell, headless env), read the URL from the CLI
output and give it to the user to open manually.
Only skip this step if whoami succeeded with a name (email) line.
If the project has a build step, run it first:
npm run build
# or: pnpm build, vite build, etc.
The build output directory (usually dist/) is what gets deployed.
vg deploy ./dist --slug my-game
./dist — the directory containing index.html and all assets--slug my-game — the subdomain name (lowercase, hyphens allowed). The game will be live at https://my-game.vibedgames.comRunning vg deploy from a project root (a directory with package.json)
automatically deploys its build output when one exists — dist/, build/,
or out/, whichever has an index.html (the root index.html of a
Vite-style project is the source template, not the game). An unbuilt project
root gets a warning. Plain-HTML games (no package.json) deploy as-is.
After deploy, the CLI prints the live URL. Open it to verify.
Playable on mobile? Deployed games are shared by link and frequently opened on phones. If the game is mouse/keyboard-only, add on-screen touch controls (a virtual joystick + buttons) so the link works on a phone — see the
gamepadskill (@vibedgames/gamepad). One prompt: "add touch controls".
Every game gets a share card automatically: when the served HTML has no
og: tags, the platform injects them — title from the game name, description
from the page's <meta name="description"> (add one!), and a cover image.
To ship a custom cover, drop og.jpg (1200×630+ landscape; og.png and
og.webp also work) into the deployed directory root (public/og.jpg in a
Vite project). No meta tags needed. To fully own share meta instead, add your
own og: tags — the platform then serves the page untouched.
dist/, build/, out/)space-invaders, my-cool-game)vibedgames.json exists in the deploy directory, the slug is read from there automaticallyCreate vibedgames.json in the project root to skip the --slug flag:
{
"slug": "my-game",
"name": "My Cool Game"
}
Then just: vg deploy ./dist
vg login first