Web Game Development Expert

Problem It Solves

Building web mini-games often fails not because code is missing, but because requirements stay vague, game loops are incomplete, state transitions break, collision detection misses, and mobile input is never validated. A prompt like “make a 3D game” still lacks camera style, controls, win/lose rules, and difficulty curve. After the first run, common bugs include blank Canvas, failed Three.js CDN load, objects passing through walls, jittering cameras, and invisible particles. This skill treats a game idea as an engineering task that can be clarified, architected, generated, and verified.

How It Works

• Requirement clarification: It extracts the core loop, win condition, lose condition, scoring, difficulty curve, feedback system, and lifecycle. For 3D projects, it also confirms camera type, movement controls, spatial boundaries, and interaction rules.
• Architecture design: It designs a closed loop across start screen, gameplay, end state, and replay path. State transitions such as IDLE, PLAYING, and GAMEOVER are made explicit, while collision matrices define what objects can hit, collect, or trigger.
• Technology selection: Simple 2D games use HTML5 Canvas and native JavaScript; more complex 2D games may use Phaser.js. 3D games are built around Three.js, with optional pointer lock, physics logic, or object pooling for performance.
• Code delivery: The output is a single runnable HTML file with CSS and JS, key sections commented, and external libraries loaded from CDNs. It then checks for the start screen, update loop, game-over detection, replay path, and collision feedback.
• Debugging and tuning: It can help trace syntax errors, missing event listeners, absent requestAnimationFrame, tunneling collisions, camera jitter, memory leaks, and particle setup issues.

Fit and Limits

It is well suited to prototypes, demos, educational mini-games, and static hosting deploys. The scope is browser-based web games, not desktop apps, native mobile apps, or multiplayer server backends. Large multiplayer projects should be broken into stages. Generated content must stay compliant, and the priority is a complete, runnable artifact before detailed explanation.