ship-web-games — Claude Code skill: what it does, how to install
Packages, deploys, and smoke-tests Three.js and web games on production. Verifies game loads, assets, and core inputs in an approved browser.
npx skills add MengTo/Skills --skill ship-web-games -a claude-codeWhat ship-web-games does
This skill guides the release workflow for web games. It locks down the integration commit, runs focused tests, and builds the production package. Only the validated commit gets deployed.
Next is the production proof step. The agent opens the deployed game in the approved browser. It checks loading, initial input, and console logs. A green local build is not enough; the skill demands verification directly on the live server.
To finish, it records release proof alongside a rollback target. It closes QA tabs and temporary dev servers, leaving active tasks from other processes untouched.
What it helps with
- verify game loading and console errors on production
- smoke-test core combat and user input in the browser
- record release proof and set a rollback target
- clean up temporary dev servers and QA tabs
Example prompts for the agent
- Deploy the validated commit of our Three.js game and run browser smoke tests
- Package the game release, verify inputs on production, and prepare a rollback target
How to install ship-web-games
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill ship-web-games -a claude-code2Manually: put the files in place
~/.claude/skills/ship-web-games/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ship-web-games/
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill ship-web-games -a codex2Manually: put the files in place
.agents/skills/ship-web-games/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill ship-web-games -a cursor2Manually: put the files in place
.cursor/skills/ship-web-games/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install MengTo/Skills ship-web-games2Manually: put the files in place
.github/skills/ship-web-games/SKILL.md1Skills CLI (Vercel)
npx skills add MengTo/Skills --skill ship-web-games -a gemini-cli2Platform CLI
gemini skills install https://github.com/MengTo/Skills --path agent-skills/game-development/ship-web-gamesManually: put the files in place
.devin/skills/ship-web-games/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add MengTo/Skills --skill ship-web-games -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ship-web-games
How to install ship-web-games in Claude Code?
Run npx skills add MengTo/Skills --skill ship-web-games -a claude-code in your terminal.
What does ship-web-games do?
It guides game release steps, deploying a validated commit, running live browser smoke tests, and recording rollback info.
What does the production proof step verify?
It checks initial load, first user input, a core combat or gameplay interaction, asset delivery, responsive layout, and console errors in an approved browser.
Source text
SKILL.md · MIT
--- name: ship-web-games description: Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources. --- # Ship Web Games Release only a verified commit and prove the deployed game, not merely the local build. ## Release sequence 1. Confirm the exact integration commit and preserve unrelated work. 2. Run focused tests, lint/type checks, production build, and diff checks. 3. Package and deploy the exact validated commit. 4. Poll deployment status and open the production game in the repository-approved browser. ## Production proof Verify load, first input, one combat or core interaction, assets, save/settings if applicable, responsive view, console health, and representative performance. Report the deployed state separately from local readiness. ## Finish cleanly Record release evidence and rollback target. Close temporary dev servers, benchmarks, and QA tabs once no longer needed; do not terminate resources owned by another active task.
© MengTo · MIT · MengTo/Skills
