What problem does it solve?
Web browser game development faces unique platform-specific constraints including inconsistent browser API support, performance throttling in background tabs, strict audio autoplay policies, and limited local file access that can cause compatibility issues, poor performance, or broken functionality without targeted guidance.
Core Features & Use Cases
- Framework Selection Decision Trees: Clear 2025 comparisons and decision flows to choose the right tool for 2D (Phaser, PixiJS), 3D (Three.js, Babylon.js), or hybrid canvas games.
- Browser Optimization Best Practices: Actionable strategies for asset compression, lazy loading, object pooling, and tab visibility handling to maximize performance across desktop and mobile devices.
- PWA & Offline Support: Step-by-step guidance to package web games as installable progressive web apps with offline play, home screen access, and push notification capabilities.
- Use Case: A developer building a casual 2D mobile puzzle game can use this skill to select PixiJS for its rendering performance, implement KTX2 texture compression to cut load times by 60%, and configure a service worker to let users play offline on commutes with spotty internet.
Quick Start
Use the web-games skill to select the optimal framework and implement performance optimizations for your new 2D browser puzzle game.