phaser-automation-kit

Automate Phaser 3 game interactions via the window.__TEST__ test seam.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/pmarashian/cursor-agent-skills --skill phaser-automation-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phaser-automation-kit
Source: https://github.com/pmarashian/cursor-agent-skills/tree/main/phaser-automation-kit
Command: npx skills add https://github.com/pmarashian/cursor-agent-skills --skill phaser-automation-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the automation of Phaser 3 games by leveraging a direct test seam (window.__TEST__) instead of brittle DOM snapshots, making automation faster and more reliable.

Core Features & Use Cases

  • Direct Game State Access: Interact with game state and logic directly through window.__TEST__.
  • Skip DOM Snapshots: Avoid unnecessary DOM inspection for canvas/WebGL-based games.
  • Use Case: Automate testing for a Phaser 3 game by directly controlling scene navigation, inspecting game state, and triggering in-game actions via the provided test seam.

Quick Start

Open the Phaser game at http://localhost:3000 with test mode enabled and then navigate to the 'GameScene'.

Frequently Asked Questions about phaser-automation-kit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Phaser 3 game testing without relying on DOM snapshots?

Automate Phaser 3 game testing by utilizing a direct JavaScript test seam (`window.__TEST__`) to bypass DOM snapshots, enabling direct game state inspection, scene navigation, and functional trigger execution for canvas/WebGL applications.

Why does DOM snapshot testing fail for WebGL and canvas games?

DOM snapshot testing often fails for WebGL and canvas games because visual elements render inside a single canvas context without distinct DOM nodes. Using a direct JavaScript test seam bypasses this limitation by accessing the underlying game state directly.

How do I navigate between scenes when automating a Phaser game?

Navigate between Phaser game scenes by calling the scene navigation methods exposed through the standardized `window.__TEST__` test seam structure. This allows automated scripts to directly control scene transitions without DOM interactions.

Do I need to modify my Phaser game code to use the phaser-automation-kit?

Yes, you must modify your Phaser game code to expose a standardized test seam structure on `window.__TEST__`. This direct manipulation and data retrieval interface is required for the automation kit to function properly.

What is the best way to inspect game state in a Phaser 3 canvas application?

Inspect Phaser 3 game state directly through a JavaScript test seam (`window.__TEST__`). This approach avoids brittle DOM inspection and allows efficient retrieval of game logic data and state variables for canvas/WebGL applications.