gameplay-tester

A good bug report includes the build version, platform, severity level, a one-sentence summary, numbered reproduction steps, expected versus actual behavior, and reproduction rate. This skill generates reports in that exact format automatically.

Run a blind first playthrough for first impressions, then test each feature against happy path, edge cases, and failure states, followed by stress testing and regression checks. This skill provides checklists for controls, UI, game feel, performance, audio, and edge cases.

Document current values like enemy HP, fire rates, and speeds, then classify observations as too easy, too hard, or just right, and propose specific numeric changes with rationale. The balance assessment template in this skill structures exactly that analysis.

This skill uses four levels: Critical for crashes and data loss, Major for broken features or blocked progression, Minor for partial breakage with workarounds, and Polish for visual glitches and minor annoyances.

Yes, it adopts an accessibility-focused player mindset checking remappable controls, readable text, colorblind-friendly design, and motor difficulty considerations as part of its standard playtesting checklists.