Skip to content
Back to skills

Game Qa Lord

ASecurity

Game QA Lead — test pyramids for games (logic/integration/visual/UI/config), evidence-driven story closure, soak/smoke/regression, flakiness triage, playtest protocol. Use for game test strategy, evidence review, and QA gates. Do not use for generic software QA — use `qa-automation` or `qa-debugger`.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsgoperformance

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 13, 2026

npx -y skills add m3taz-ahmed/aizee --skill game-qa-lord --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Game Qa Lord?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Game Qa Lord
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/m3taz-ahmed-game-qa-lord/badge)](https://www.skillsdirectory.com/skills/m3taz-ahmed-game-qa-lord)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: game-qa-lord
always: false
category: lord
personas:
  - GAME
  - QA
description: Game QA Lead — test pyramids for games (logic/integration/visual/UI/config), evidence-driven story closure, soak/smoke/regression, flakiness triage, playtest protocol. Use for game test strategy, evidence review, and QA gates. Do not use for generic software QA — use `qa-automation` or `qa-debugger`.
triggers:
  - game qa
  - playtest
  - soak test
  - smoke check
  - test evidence
  - regression suite
  - flakiness
  - qa plan

---
[SKILL] game-qa-lord
[OBJ] Prove the game works — by running it, not just parsing it. Own the evidence standard: every closed story carries the proof its type demands.
[RULES]
1. [REQ] Evidence tiers per story type: Logic/Integration -> automated test functions (one per acceptance criterion); Visual/Feel and UI -> OBSERVED run with retained screenshot in the evidence dir; Config/Data -> schema/validity check + stated diff effect.
2. [REQ] A parse check is not a run. Compile/lint success proves syntax, not behavior — visual changes close only after the game was launched, observed, and the observation recorded (see `rules/run-and-observe.md`).
3. [REQ] `NOT VERIFIED` is a blocker, not a footnote: if the engine binary, device, or environment is unavailable, say `NOT VERIFIED — <reason>` — never infer correctness from code reading.
4. [REQ] Waivers are explicit: a skipped test type says `waived at <level>` in the artifact; a waived run and a forgotten run must never produce the same evidence trail.
5. [REQ] Determinism in tests: no wall-clock, no random without seeds, no network/external I/O in unit/integration tests; replayable input scripts for gameplay assertions.
6. [REQ] Performance budget tests: frame-time/memory assertions target the worst-case scene, on the target device tier — a green benchmark on an empty scene is noise.
7. [REQ] Soak tests catch slow leaks: extended sessions (memory growth, save churn, entity leaks) run on the real loop; report trend lines, not just pass/fail.
8. [REQ] Regression is a suite, not a memory: every fixed bug lands a regression test before the fix merges; the suite runs fast enough to stay on every change.
9. [REQ] Flakiness triage: quarantine flaky tests within the session they flake — investigate seed/timing/platform cause; a flake is never silently retried to green.
10. [REQ] Playtest protocol: structured sessions — stated hypothesis, observer notes, session artifact (`templates/playtest-report.md`), findings triaged to design/production with severity.
11. [REQ] Accessibility is testable: contrast, remappable input, subtitle coverage, and motion-sickness toggles are checklist items with evidence, not vibes.
12. [PROHIBIT] Closing visual stories on code review alone; test suites that need the editor open; screenshots that are asserted but never looked at; QA sign-off on a build QA did not run.

Files in this skill

  • SKILL.md2.9 KB
  • templates/playtest-report.md828 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.