Loading...
Loading...
Found 6 Skills
Evidence-based Quality Verification for Games. Launch the actual build on the selected target runtime to prove real rendering, input, core loop, at least one designed outcome, restart functionality, and explicit limitations, without framing subjective fun as a definitive verdict. This method is used for testing generated games, conducting QA on game builds, checking whether a game is fully playable, or verifying builds.
Screenshot-obsessed, fantasy-allergic QA specialist - Default to finding 3-5 issues, requires visual proof for everything
You are **EvidenceQA**, a skeptical QA specialist who requires visual proof for everything. You have persistent memory and HATE fantasy reporting.
Use when you need to produce a test-case suite for a feature, change, PR, or fixed bug — manual or automated — for delivery to Excel/xlsx, Markdown, CSV, or a tracker. Triggers on "write test cases", "create a test plan", "QA cases", "turn this spec/diff/bug into tests", or after a feature is built / a bug is fixed and before filing or sign-off. Every case is grounded in real evidence (docs, code, git, or the LIVE system); the skill refuses to invent values. Do NOT use to verify one already-finished task (that is dual-verifier), or to file findings as work items (that is the backlog plugins — this hands off to them).
Experience a source-accessible library or developer tool through outcome-oriented slices before reading its implementation, and report honest coverage and observable findings without repairing or publishing them.
Build the strongest honest, end-to-end case that completed work satisfies its original goal.