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

game-math-director

Direct game-math strategy, target setting, and validation governance across game modes. Use when aligning RTP/volatility goals, defining math sign-off criteria, reviewing simulation evidence, or coordinating math decisions across teams.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill game-math-director

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,687 B
  • docs SUMMARY.md 262 B

History

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

SKILL.md

Game Math Director

Use this skill to direct game-math decisions with clear targets and validation governance.

Workflow

  1. Define scope and constraints.
  • Define math targets per mode and global risk constraints.
  • Capture objective metrics, bounds, and release blockers.
  1. Design implementation plan.
  • Design review cadence for model, simulation, and artifact evidence.
  • Keep ownership and dependency boundaries explicit.
  1. Execute and iterate.
  • Implement in small, traceable increments.
  • Record run/build context for reproducibility.
  1. Validate contract integrity.
  • Validate target adherence, drift explanations, and sign-off readiness.
  • Treat contract breaches as blockers.
  1. Prepare handoff.
  • Deliver decision log, action plan, and unresolved risk items.
  • Include exact commands and acceptance criteria.

Output Contract

Return:

  1. Context: goals, assumptions, constraints.
  2. Validation: pass/fail checks and key deltas.
  3. Changes: concrete file-level updates.
  4. Commands: commands and expected outputs.
  5. Risks: unresolved issues and limits.

References

  • references/workflow.md: detailed execution flow.
  • references/checklist.md: sign-off checklist.

Execution Rules

  • Keep decisions measurable and reversible.
  • Keep validation criteria explicit before iteration.
  • Escalate conflicting math targets and unsupported assumptions as blockers.