How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill autoplay-system-designerBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Autoplay System Designer
Use this skill to design casino-grade auto-play behavior with clear stop rules, safe UI states, and compliance-ready confirmations.
Core Principles
- Auto-play must be explicit, reversible, and visible at all times.
- Auto-play never bypasses required confirmations for high-cost modes.
- Stop conditions are deterministic and checked before each spin.
Workflow
- Define auto-play scope.
- Max spins, stop on win/loss, stop on feature trigger.
- Decide what happens on connection loss or errors.
- Define UI states.
- Spin button becomes Stop during auto-play.
- Show remaining spins and active stop conditions.
- Define confirmation flow.
- Require confirmation before start.
- Show cost multipliers or special mode costs.
- Define stop rules.
- Manual stop always overrides.
- Stop on balance below min bet.
- Stop on session invalidation or compliance errors.
- Prepare QA matrix.
- Single spin, multiple spins, feature trigger, error recovery.
Output Contract
Return:
Auto-Play Policy: limits, counters, stop conditions.UI Mapping: button state, counters, labels.Confirmation Flow: modal content and gating rules.Error Handling: resume/stop policy and user messaging.Verification: test matrix and pass criteria.Risks: edge cases or ambiguity.
Commands
bash
python3 scripts/validate_autoplay_spec.py \
--input <path/to/autoplay_spec.json>Treat non-zero exits as blocker findings.
References
references/workflow.md: autoplay design flow.references/contracts.md: autoplay spec contract.references/checklist.md: UX and compliance checks.references/signoff-template.md: sign-off template.
Execution Rules
- Auto-play must always expose a Stop control.
- Never allow one-click auto-play start without confirmation.
- Avoid restricted wording in social jurisdictions.
