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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill engine-selection --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) 1. **Platform:** Web, mobile, PC, console, VR? 2. **Primary loop:** Action/physics, turn-based, narrative branch, management/UI, hybrid? 3. **Presentation:** Full-screen canvas, DOM/UI chrome, or both? 4. **Toolchain:** No-build / ESM OK, or bundler + editor OK? 5. **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? │
- Fit questions (ask first)
- Architecture patterns
- Web — decision tree
- Quick comparison (web & common exports)
- Non-web defaults (see also platform skills)
- Anti-patterns
- When to Use
- Limitations
What does the engine-selection skill do?
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.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill engine-selection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.