web-game-development

name	web-game-development
description	Route Three.js and browser game-development requests into the narrowest matching sub-skill of the 19-skill MengTo/Skills game-development family — level authoring, map editing, cameras, enemy systems and AI, monster rigs, action combat, encounter design, inventory, hybrid/Vesperfall assets, VFX, audio feedback, mobile controls, performance tuning, QA, changelogs, and release. Use when a task touches any of those for a playable web game, and fetch the matching sub-skill before doing the work instead of improvising. Route Unity/C# engine work to `unity-gamedev-skill-pack` instead. Triggers on: three.js game, browser game, webgl game, isometric arpg, enemy AI, game camera, game inventory, game VFX, game audio feedback, ship web game, playtest web game, mobile threejs game, game encounter design, monster rig, hybrid game assets.
allowed-tools	Bash Read Write Edit Glob Grep
compatibility	Best for Three.js, WebGL, and browser-native game repositories where the task is choosing and fetching the correct upstream MengTo/Skills sub-skill. Not for Unity/C# or Unreal engine work, generic web-app (non-game) performance, CI/CD pipeline design, or Steam marketing ops — route those elsewhere.
license	MIT
metadata	{"tags":"game-development, three.js, webgl, browser-games, skill-routing, skill-pack, mengto-skills","version":"1.0","source":"https://github.com/MengTo/Skills/tree/main/agent-skills/game-development"}

Web Game Development

Use this skill when the real question is "which upstream Three.js/browser game-development skill should own this task, and how do I get it installed?"

This is a routing pack, not a reimplementation. The 19 real sub-skills live upstream at MengTo/Skills. The job here is to:

1. classify the task honestly against the 19 sub-skills,
2. pick the single narrowest match (combine only when the task truly crosses a documented boundary),
3. fetch that sub-skill locally if it is not already installed,
4. sequence multi-skill work along the game lifecycle, and
5. route out to this repo's non-Three.js skills when they are the real owner.

Read references/skill-routing-table.md for the full 19-skill decision table with upstream-grounded "use when" lines and boundary notes. Read references/lifecycle-and-handoffs.md for the prototype → systems → content → assets → feel → perf → QA → release ordering and which sub-skills own each stage. Read references/route-outs.md before routing to unity-gamedev-skill-pack, game-performance-profiler, game-ci-cd-pipeline, game-build-log-triage, game-demo-feedback-triage, steam-store-launch-ops, or perfectpixel.

Explicit boundary against unity-gamedev-skill-pack

unity-gamedev-skill-pack curates external Unity/C# skill packs (Addressables, Cinemachine, GAS, VContainer, UniTask, Wwise). This skill, web-game-development, routes into the Three.js / browser game-development family instead. If the engine is Unity or Unreal, stop here and use unity-gamedev-skill-pack (or the engine-specific Unity/Unreal skills such as game-performance-profiler, game-ci-cd-pipeline, game-build-log-triage described in references/route-outs.md). Do not apply Three.js-authored sub-skill guidance to a Unity project or vice versa.

When to use this skill

• The task is building, extending, or auditing a Three.js/browser action game
• You need to pick between two or more upstream game-development sub-skills and are not sure which one is narrowest
• The upstream sub-skill needed for the task is not yet installed locally