Three.js Lite

Use this skill when a user wants a 3D browser game with minimal rendering complexity and stable mobile performance.

Workflow

Start from assets/starter-single-file.html.
Implement one camera, one scene, one gameplay loop.
Add player input and terminal condition before adding visual polish.
Keep geometry/material count small and predictable.
If targeting Remix/Farcade, apply hooks in references/remix-farcade-integration.md.
Validate required hooks (gameOver, onPlayAgain, onToggleMute) before handoff.

Keep draw calls low and avoid postprocessing by default.
Prefer simple MeshBasicMaterial/MeshStandardMaterial setups.
Avoid dynamic shadows on first pass.
For Remix uploads, output single-file HTML with inline JS/CSS unless user asks otherwise.
For Remix uploads, include <script src="https://cdn.jsdelivr.net/npm/@farcade/game-sdk@0.3.0/dist/index.min.js"></script> in HTML <head>.
Treat 3D as optional style; gameplay clarity is higher priority than visual complexity.

references/threejs-mobile-patterns.md for scene setup, controls, and perf budgets.
references/remix-farcade-integration.md for SDK hooks required by Remix validation.