인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
개발 및 엔지니어링 · SKILL.md

web-games

web-games

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: web-games description: Web browser game development principles. Framework selection, WebGPU, optimization, PWA. allowed-tools: Read, Write, Edit, Glob, Grep

Web Browser Game Development

Framework selection and browser-specific principles.


1. Framework Selection

Decision Tree

What type of game?
│
├── 2D Game
│   ├── Full game engine features? → Phaser
│   └── Raw rendering power? → PixiJS
│
├── 3D Game
│   ├── Full engine (physics, XR)? → Babylon.js
│   └── Rendering focused? → Three.js
│
└── Hybrid / Canvas
    └── Custom → Raw Canvas/WebGL

Comparison (2025)

FrameworkTypeBest For
Phaser 42DFull game features
PixiJS 82DRendering, UI
Three.js3DVisualizations, lightweight
Babylon.js 73DFull engine, XR

2. WebGPU Adoption

Browser Support (2025)

BrowserSupport
Chrome✅ Since v113
Edge✅ Since v113
Firefox✅ Since v131
Safari✅ Since 18.0
Total~73% global

Decision

  • New projects: Use WebGPU with WebGL fallback
  • Legacy support: Start with WebGL
  • Feature detection: Check navigator.gpu

3. Performance Principles

Browser Constraints

ConstraintStrategy
No local file accessAsset bundling, CDN
Tab throttlingPause when hidden
Mobile data limitsCompress assets
Audio autoplayRequire user interaction

Optimization Priority

  1. Asset compression - KTX2, Draco, WebP
  2. Lazy loading - Load on demand
  3. Object pooling - Avoid GC
  4. Draw call batching - Reduce state changes
  5. Web Workers - Offload heavy computation

4. Asset Strategy

Compression Formats

TypeFormat
TexturesKTX2 + Basis Universal
AudioWebM/Opus (fallback: MP3)
3D ModelsglTF + Draco/Meshopt

Loading Strategy

PhaseLoad
StartupCore assets, <2MB
GameplayStream on demand
BackgroundPrefetch next level

5. PWA for Games

Benefits

  • Offline play
  • Install to home screen
  • Full screen mode
  • Push notifications

Requirements

  • Service worker for caching
  • Web app manifest
  • HTTPS

6. Audio Handling

Browser Requirements

  • Audio context requires user interaction
  • Create AudioContext on first click/tap
  • Resume context if suspended

Best Practices

  • Use Web Audio API
  • Pool audio sources
  • Preload common sounds
  • Compress with WebM/Opus

7. Anti-Patterns

❌ Don't✅ Do
Load all assets upfrontProgressive loading
Ignore tab visibilityPause when hidden
Block on audio loadLazy load audio
Skip compressionCompress everything
Assume fast connectionHandle slow networks

Remember: Browser is the most accessible platform. Respect its constraints.

저장한 Skills