egorfedorov/slot-casino-game-developer-skills-for-stake-engine

slot-qa-engineer

Design and execute test plans for slot games covering math correctness, UI logic, performance, and compliance. Use when validating game rules, running regression tests, verifying error handling, checking jurisdiction constraints, or preparing release sign-off reports.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill slot-qa-engineer

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from egorfedorov/slot-casino-game-developer-skills-for-stake-engine · top by installs.

npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine

Browse all from egorfedorov/slot-casino-game-developer-skills-for-stake-engine

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,502 B
  • docs SUMMARY.md 292 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Slot QA Engineer

Use this skill to ensure game quality, stability, and compliance before release.

Workflow

  1. Analyze Requirements.
  • Review math model, game rules, and UI specifications.
  • Identify edge cases (max win, zero balance, network disconnects).
  1. Design Test Plan.
  • Define test cases for functional, regression, and performance testing.
  • Create cheat/debug commands for triggering features.
  1. Execute Testing.
  • Run manual tests for UX flow and animation glitches.
  • Run automated tests for math verification and stability.
  • Verify compliance with jurisdiction rules (e.g., reality checks, time limits).
  1. Report and Track.
  • Log defects with reproduction steps and severity.
  • Verify fixes and perform regression testing.
  1. Final Sign-off.
  • Validate against release checklist.
  • confirm all critical and high-priority bugs are resolved.

Output Contract

Return:

  1. Test Plan: coverage matrix and test cases.
  2. Bug Report: list of identified issues with priority.
  3. Sign-off Report: pass/fail status and residual risks.

References

  • references/workflow.md: QA process and stages.
  • references/test-plan.md: Template for test planning.