What problem does it solve?
This Skill helps you choose the right framework and architecture for browser games while avoiding common performance, asset, and browser-permission pitfalls.
Core Features & Use Cases
- Framework selection by game type: Choose Phaser for full-feature 2D, PixiJS for rendering/UI-focused 2D, Three.js for lightweight 3D, or Babylon.js for full 3D engines and XR.
- WebGPU adoption strategy with fallbacks: Use WebGPU when available and gracefully fall back to WebGL to support more users.
- Performance-first asset and runtime guidance: Apply compression, lazy loading, object pooling, draw-call batching, and Web Workers to reduce stutter and memory pressure.
- PWA readiness for games: Add service workers, a web app manifest, and HTTPS so the game can install and work offline.
- Audio compliance and UX: Respect autoplay restrictions by creating/resuming AudioContext only after user interaction.
Quick Start
Use the web-games skill to design a new browser game plan that selects Phaser or PixiJS for 2D, targets WebGPU with WebGL fallback, and outlines a PWA-capable asset-loading and audio strategy.