Goal

Use one end-to-end engineering skill for three.js game work. Select only the relevant internal tracks, preserve cross-system boundaries, and produce an implementation or review that is runnable, measurable, disposable, and releaseable.

This skill replaces the former threejs-game-* installable family. Do not route work to child skills or require users to install additional Three.js skills.

Activation

Use this skill when the work includes one or more of:

• a persistent frame loop, gameplay state, player control, collision, animation, saving, networking, or XR
• turning a three.js demo into a maintainable game codebase
• adding or auditing assets, rendering, interaction, physics, VFX, performance, testing, or release workflows for a game
• diagnosing a cross-system game issue whose root cause may span runtime, assets, rendering, input, physics, or lifecycle management

Do not use it for a static product viewer, marketing scene, data visualization, or decorative 3D page unless game-like runtime and interaction constraints are materially present.

Required context