testador-jogos

Tests games hands-on with player personas and produces QA bug reports and critical reviews.

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill testador-jogos-codjeremias-cell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testador-jogos
Source: https://github.com/codjeremias-cell/Orquestrador-fable/tree/main/skills/testador-jogos
Command: npx skills add https://github.com/codjeremias-cell/Orquestrador-fable --skill testador-jogos-codjeremias-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve? Game developers lack structured playtesting that combines real bug hunting with honest design critique, leaving prototypes shipped with crashes, broken state resets, and unbalanced gameplay. ## Core Features & Use Cases - Persona-driven playtesting: Plays the game through four personas (novice, casual, hardcore, adversarial destroyer) via a Playwright harness, each surfacing a different class of problems. - Reproducible bug reports: Documents every defect with numbered reproduction steps, expected vs. actual results, severity classification (A/B/C), and screenshot or console evidence. - Critical analysis with rubric: Scores 8 design categories (onboarding, controls, mechanics, balance, UX/UI, audio/visual, content, fun) on a 0-10 anchored rubric with a weighted overall verdict. - Use Case: Point it at your HTML5 game jam prototype and receive a QA report, a prioritized improvement plan in waves, and a reusable regression checklist for future builds. ## Quick Start Use the testador-jogos skill to playtest my game at this URL and deliver a bug report, critical review, and regression checklist.

Frequently Asked Questions about testador-jogos

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

FAQPage Schema
How do I test my HTML5 game for bugs automatically?▼

Provide the game URL or HTML file and the skill plays it via a Playwright harness, executing smoke tests, persona sessions, and adversarial input attacks. Every bug found is documented with reproduction steps, severity, and screenshot or console evidence.

What does a game QA playtest report include?▼

The report contains an executive summary, bugs grouped by severity (A/B/C), a critical analysis scoring 8 design categories on a 0-10 rubric, per-persona session results, and declared test limitations. It ships alongside an improvement plan and regression checklist.

Can I get game design feedback without a playable build?▼

Yes, document mode analyzes a GDD, video, or screenshots and delivers design critique, red flags, and a test plan for the future build. It never fabricates bugs or claims to have played, marking unassessable categories as not evaluable without a build.

Does the Playwright game tester work in headless environments?▼

Yes, Chromium runs headless with WebGL via SwiftShader, but audio, gamepad, and fullscreen require a real device and are flagged as limitations. Emoji rendering as tofu boxes and absolute FPS values are known headless artifacts, not game bugs.

When should I use game playtesting instead of code test suites?▼

Use this skill for gameplay experience testing: bugs found by playing, design evaluation, and fun assessment. For static and dynamic code-level test batteries with PASS/FAIL on systems or backends, a system tester skill is the right tool instead.