phaser-2d-arcade
Build mobile-first 2D browser games with Phaser 3 Arcade Physics
Best use case
phaser-2d-arcade is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Build mobile-first 2D browser games with Phaser 3 Arcade Physics
Teams using phaser-2d-arcade should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/phaser-2d-arcade/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How phaser-2d-arcade Compares
| Feature / Agent | phaser-2d-arcade | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Build mobile-first 2D browser games with Phaser 3 Arcade Physics
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Phaser 2D Arcade Use this skill when a user asks for a Phaser browser game, especially for fast single-file 2D gameplay loops. ## Workflow 1. Start from `assets/starter-single-file.html`. 2. Implement core loop first: `boot -> preload -> create -> update`. 3. Add win/lose condition and scoring before polish. 4. Add touch controls and responsive layout early (mobile-first). 5. If targeting Remix, apply SDK hooks from `references/sdk-integration.md`. 6. Validate required hooks (`gameOver`, `onPlayAgain`, `onToggleMute`) before handoff. ## Guardrails - Prefer Phaser Arcade Physics for simplicity/performance. - Keep initial scope small: 1 scene, 1 mechanic, 1 fail condition. - Avoid expensive per-frame allocations and unnecessary visual effects. - Keep gameplay restart-safe and deterministic. - For Remix uploads, produce single-file HTML with inline JS/CSS unless user asks otherwise. - For Remix uploads, include `<script src="https://cdn.jsdelivr.net/npm/@remix-gg/sdk@latest/dist/index.min.js"></script>` in HTML `<head>`. ## References - `references/phaser-arcade-patterns.md` for scene architecture, controls, and perf defaults. - `references/sdk-integration.md` for Remix SDK hooks and integration shape.
Related Skills
threejs-lite
Build lightweight mobile-friendly 3D browser games with Three.js
remix-upload-game
Upload and validate HTML game code for Remix. Use when creating or updating a draft version through the CLI, MCP tools, or direct REST calls.
remix-upload-asset
Upload images, audio, or 3D models as hosted game assets
remix-submission-rules
Validation and publish constraints for Remix game submissions
remix-shop-items
Create, update, delete, and integrate Remix shop items. Use when a game needs Bits items, consumables, one-time unlocks, tier unlocks, store icons, or purchase handling in @remix-gg/sdk code.
remix-save-game
Add save and load game state functionality via RemixSDK
remix-rest-snippets
REST client snippets for Remix agent publishing
remix-open-game
Open a game in the Remix Studio browser for preview and editing
remix-multiplayer
Enable multiplayer support for a Remix game
remix-game-sdk
Reference for the current @remix-gg/sdk runtime. Use when generating or repairing Remix game code, shop item integrations, save-state flows, multiplayer hooks, or host-safe mobile UI behavior.
remix-game-creation
Create a new game draft via the Remix API
remix-game-best-practices
Mobile-first game creation best practices for Remix