engine-selection
Selects game engines and frameworks by platform, genre, and architecture (full canvas shell vs hybrid DOM shell + guest viewport). Covers Phaser, PixiJS, Kaplay, Canvas/WebGL, Three.js, Babylon.js, Godot, Unity, Ink, Twine. Use when choosing a stack or comparing runtimes before implementation.
Engine selection
Pick tools that match delivery target, interaction model, and team constraints. Engines serve the game type — not the reverse.
Fit questions (ask first)
- Platform: Web, mobile, PC, console, VR?
- Primary loop: Action/physics, turn-based, narrative branch, management/UI, hybrid?
- Presentation: Full-screen canvas, DOM/UI chrome, or both?
- Toolchain: No-build / ESM OK, or bundler + editor OK?
- Authoring: Code-only, or designers need Twine/Ink/Godot/Unity editors?
Architecture patterns
| Pattern | When | Notes |
|---|---|---|
| Full engine shell | Game is the canvas/scene | Phaser, Godot, Unity, Kaplay as app root |
| Renderer + custom logic | You want draw power, own gameplay | PixiJS, Three.js + your systems |
| Hybrid shell + guest | Dense UI/text + occasional skill-checks | DOM/app shell; mount canvas engines in modals/viewports only |
| Narrative runtime | Branching prose is the product | Ink, Twine; host chrome separately |
| Content-as-data | Levels/events authored as packs | JSON/YAML + thin loader; engine optional |
Web — decision tree
What type of game?
│
├── Mostly DOM / panels / forms / text UI
│ ├── + small arcade/spatial challenges
│ │ └── Hybrid: custom shell + guest
│ │ Raw Canvas/WebGL → Kaplay → Phaser → PixiJS
│ Subscribers only
The full skill, its 1 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | self |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md |
| Added | 2026-07-17 |
Related skills
2d-games
2D game development principles. Sprites, atlases, tilemaps, physics, cameras, and genre patterns (platformer, top-down). Use for canvas/Phaser/Kaplay/Pixi 2D games or guest viewports inside hybrid web apps.
game-art
Game art principles. Visual style selection, asset pipeline, animation workflow.
game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
game-development
Game development orchestrator. Routes by platform, dimension, and engine fit (web 2D/3D, hybrid DOM+canvas, narrative tools). Use when starting or structuring a game project, choosing frameworks, or picking among Phaser, PixiJS, Kaplay, Canvas/WebGL, Three.js, Babylon.js, Godot, Unity, or Ink/Twine.