Game Playtest

Overview

Use this skill to test browser games the way players experience them: through boot, input, scene transitions, HUD readability, and visual state changes. Prefer browser automation and screenshot review when the project supports it.

Preferred Workflow

1. Boot the game and confirm the first actionable screen.
2. Exercise the main verbs.
3. Capture screenshots from representative states.
4. Check the UI layer independently from the render layer.
5. Report findings in severity order with reproduction steps.

Tooling Guidance

• Prefer Playwright or equivalent browser automation already available in the repo.
• When the game is canvas or WebGL heavy, screenshots are mandatory because DOM assertions alone miss visual regressions.
• Use screenshots to judge playfield obstruction and HUD weight, not just correctness of text or layout.