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

ui-slot-ux-designer

Design, review, and validate slot game UI/UX flows for desktop and mobile play.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill ui-slot-ux-designer

Summary

  • Design, review, and validate slot game UI/UX flows for desktop and mobile play.
  • Use when defining control hierarchy, spin-state UX, bet/balance presentation, modal interactions, responsive layouts, accessibility constraints, animation-feedback timing, or release readiness checks for slot user experience contracts.

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 2,290 B
  • docs SUMMARY.md 342 B

History

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

SKILL.md

UI Slot UX Designer

Use this skill to turn slot UX ideas into explicit, testable interaction contracts.

Workflow

  1. Define UX scope and player flow.
  • Capture session entry, betting, spin cycle, result feedback, and exit states.
  • Define desktop/mobile differences explicitly.
  1. Establish control hierarchy.
  • Define primary controls (spin/bet) and secondary controls (autoplay/turbo/settings).
  • Set visibility and priority rules by viewport and game state.
  1. Model states and interactions.
  • Define UX states and allowed transitions.
  • Map interaction triggers to target states and feedback timing.
  • Explicitly define disabled/blocked behavior during spin/resolve phases.
  1. Enforce accessibility and responsiveness.
  • Validate touch targets, reduced-motion support, and contrast-aware behavior.
  • Verify control layout works at defined breakpoints.
  1. Validate and hand off.
  • Run contract validation and classify blockers.
  • Deliver patch plan for UI components/state handlers.

Commands

python3 scripts/validate_slot_ux_spec.py \
  --input <path/to/slot_ux_spec.json>

Treat non-zero exits as blocker findings.

Output Contract

Return:

  1. UX Map: views, controls, states, and interactions.
  2. Validation Findings: pass/fail checks with exact failures.
  3. Patch Plan: component/state files to adjust.
  4. Verification: command outputs and success criteria.
  5. Residual Risks: unresolved usability/accessibility risks.

References

  • references/workflow.md: end-to-end slot UX design process.
  • references/ux-rules.md: control, feedback, and accessibility rules.
  • references/signoff-template.md: release handoff template.

Execution Rules

  • Keep spin-cycle controls deterministic by state.
  • Keep mobile-first touch safety and clarity as hard constraints.
  • Keep feedback timing explicit and bounded.
  • Flag inaccessible or ambiguous control behavior as blockers.