ship-web-games

Package, deploy, and verify playable Three.js web games in production.

5.7k|685|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/MengTo/Skills --skill ship-web-games
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-web-games
Source: https://github.com/MengTo/Skills/tree/main/agent-skills/game-development/ship-web-games
Command: npx skills add https://github.com/MengTo/Skills --skill ship-web-games

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a web game often stops at a passing local build, leaving teams unsure whether the deployed version actually loads, plays, and performs correctly for real users. This Skill enforces a disciplined release workflow that proves the production deployment, not just the local build.

Core Features & Use Cases

  • Verified Release Sequence: Confirms the exact integration commit, runs focused tests, lint/type checks, production builds, and diff checks before deploying only the validated commit.
  • Production Smoke Testing: Verifies load, first input, core gameplay interaction, assets, save/settings, responsive view, console health, and representative performance in the live environment.
  • Clean Release Finish: Records release evidence and rollback targets, then closes temporary dev servers, benchmarks, and QA tabs without touching resources owned by other tasks.
  • Use Case: After finishing a Three.js game feature, use this Skill to deploy the exact tested commit, open the production URL in a browser, confirm gameplay works end to end, and document rollback readiness.

Quick Start

Use the ship-web-games skill to release and verify this playable web game in production.

Frequently Asked Questions about ship-web-games

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Three.js web game to production?

Deploy a Three.js web game by confirming the exact integration commit, running focused tests, lint and type checks, and a production build, then packaging and deploying only that validated commit. Poll the deployment status and open the live game in a browser to confirm it works.

How to smoke test a web game after deployment?

Smoke test a deployed web game by verifying page load, first input, one core gameplay interaction, asset loading, save and settings behavior, responsive view, console health, and representative performance. Report the deployed state separately from local readiness.

Why verify the deployed game instead of the local build?

Local builds can pass while production fails due to asset paths, build configuration, or hosting differences. Verifying the deployed game proves real users can load and play it, and separates production evidence from local readiness.

What should a web game release checklist include?

A web game release checklist should include confirming the integration commit, running tests and production builds, deploying the validated commit, browser-based production proof, recording release evidence and rollback targets, and closing temporary QA resources.

When should I clean up dev servers and QA tabs after release?

Clean up temporary dev servers, benchmarks, and QA tabs only after release evidence and rollback targets are recorded and they are no longer needed. Never terminate resources owned by another active task.