stake-game-developer

End-to-end Stake game development workflow for math, RGS contract, frontend playback, and compliance gating. Use when building or updating Stake games, defining game modes and RTP targets, validating generated books/index metadata, validating event streams, integrating frontend event playback, implementing RGS communication and replay mode, or preparing publication checks including social-language and jurisdiction requirements.

跳到安装

仓库: egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine
最近来源活动: 2026年2月21日 01:07
检测到的 SKILL.md 语言: 英语
星标: 44
分支: 12

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine --skill stake-game-developer

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

17 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

Stake Game Developer

Use this skill to design, validate, and ship Stake games with deterministic event playback and compliance gates.

Workflow

Define or review the game brief, modes, and constraints. Load references/workflow.md.

Validate book/index integrity before UI assumptions. Run scripts/validate-books-index.mjs.

Validate event stream contract and sequencing. Run scripts/validate-rgs-events.mjs.

Validate frontend integration expectations. Load references/frontend-integration.md and references/rgs-event-contract.md.20→ 5. Run compliance gate checks before release review. 21→ Run scripts/audit-checklist.mjs using references/compliance-rules.json and references/compliance-checklist.md. 22→ 23→ 6. Final Approval Check. 24→ Validate full game against references/game-approval-checklist.md (PreChecks, Math, Frontend, Jurisdiction). 25→ 26→ ## Commands```bash node scripts/validate-books-index.mjs --index <path/to/index.json> --format text node scripts/validate-rgs-events.mjs --input <path/to/events.jsonl> --format text node scripts/audit-checklist.mjs --rules references/compliance-rules.json --target --social true --format text

Treat non-zero exits as hard blockers for release readiness. ## References - `references/workflow.md`: End-to-end process and required gates. - `references/book-generation-validation.md`: Book generation and index validation expectations. - `references/rgs-event-contract.md`: Required event order and field expectations. - `references/frontend-integration.md`: Deterministic player integration patterns.40→ - `references/compliance-checklist.md`: Stake checklist and jurisdiction requirements. 41→ - `references/compliance-rules.json`: Machine-readable restricted phrase and required-phrase checks. - `references/game-approval-checklist.md`: Comprehensive QA/Release sign-off gates. - `references/stake-engine-rgs.md`: Stake Engine RGS API and wallet flow details. - `references/stake-engine-replay.md`: Stake Engine replay mode requirements. - `references/stake-engine-frontend-checklist.md`: Frontend compliance checklist. - `references/currency-rules.md`: **CRITICAL** formulas for API (x1e6) vs Book (x100) scaling. 43→ 44→ ## Execution Rules - **Strict Currency/Math Scaling:** - **API (Wallet/RGS):** Use `1,000,000` scale. `display = api / 1e6`, `api = display * 1e6`. - **Books (Math/Events):** Use `100` scale. `multiplier = bookVal / 100`, `win = bet * (bookVal / 100)`. - *Never* mix these scales. See `references/currency-rules.md`. - Keep frontend stateless: never re-calculate payouts if events already provide them. - Validate data contracts before tuning UX or animation details. - Enforce compliance checks by default (`--social true`) unless user explicitly says otherwise. - When reporting findings, include file path and line when available.