Slot Mechanics Designer logo

Slot Mechanics Designer

Community
egorfedorov
slot-mechanics-designer

Design, review, and harden slot feature mechanics from product idea to implementation-ready behavior spec. Use when defining feature triggers, state transitions, retrigger rules, multipliers, respins, bonus entry/exit flow, mechanic sequencing, anti-loop constraints, or pre-implementation mechanic validation.

Overview

Publisheregorfedorov
RepositorySlot-Casino-Game-Developer-Skills-for-Stake-Engine
Skill nameslot-mechanics-designer
Stars
63
Forks
16
Bundled files
5
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by egorfedorov on GitHub. Read the source before you install it.

Installation

Install the Slot Mechanics Designer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine.git /tmp/Slot-Casino-Game-Developer-Skills-for-Stake-Engine
mkdir -p .claude/skills
cp -r /tmp/Slot-Casino-Game-Developer-Skills-for-Stake-Engine/slot-mechanics-designer .claude/skills/slot-mechanics-designer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Slot Mechanics Designer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Slot Mechanics Designer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Slot Mechanics Designer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Slot Mechanics Designer

Use this skill to convert mechanic ideas into deterministic state/trigger/action specs that engineering and math teams can implement safely.

Workflow

  1. Define mechanic scope and constraints.
  • Capture core loop, feature list, target experience, and hard constraints (max win, duration caps, retrigger limits).
  • Separate product goals from implementation assumptions.
  1. Model states and transitions first.
  • Define explicit states (base, feature, bonus, terminal as needed).
  • Define transition events and guard conditions.
  • Require deterministic entry and exit paths for each feature.
  1. Define trigger and action contracts.
  • For each mechanic, specify triggerEvent, entryState, targetState, and actions.
  • Keep action payloads explicit (for example spins/multiplier/value).
  • Enforce retrigger and cooldown behavior explicitly.
  1. Validate graph integrity before implementation.
  • Ensure all transitions reference known states.
  • Ensure non-terminal states are reachable and have exits.
  • Ensure mechanics map to valid transitions.
  1. Package handoff spec.
  • Deliver state graph, mechanic table, event contract, and known risks.
  • Include exact patch plan for implementation files.

Commands

bash
python3 scripts/check_mechanics_spec.py \
  --input <path/to/mechanics_spec.json>

Treat non-zero exits as blocker findings.

Output Contract

Return:

  1. Mechanic Map: states, transitions, mechanics, and action payloads.
  2. Validation Findings: graph consistency and trigger/action coverage with pass/fail.
  3. Patch Plan: file-level implementation steps.
  4. Verification: commands and expected success criteria.
  5. Residual Risks: unresolved design or implementation blockers.

References

  • references/workflow.md: step-by-step mechanics design process.
  • references/mechanics-patterns.md: proven feature patterns and guardrails.
  • references/signoff-template.md: final handoff template.

Execution Rules

  • Make state transitions explicit; avoid implicit side effects.
  • Cap feature loops and retriggers to prevent runaway rounds.
  • Keep mechanics deterministic and replay-friendly.
  • Flag any unreachable or non-terminating state as a blocker.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Slot Mechanics Designer AI skill do?

Design, review, and harden slot feature mechanics from product idea to implementation-ready behavior spec. Use when defining feature triggers, state transitions, retrigger rules, multipliers, respins, bonus entry/exit flow, mechanic sequencing, anti-loop constraints, or pre-implementation mechanic validation.

Why use Slot Mechanics Designer on TypingMind?

Because you install it once and use it with any model. Slot Mechanics Designer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Slot Mechanics Designer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine/tree/main/slot-mechanics-designer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Slot Mechanics Designer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Slot Mechanics Designer?

As many as you like. As long as a model supports skills, you can use Slot Mechanics Designer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Slot Mechanics Designer AI skill free?

It is published on GitHub by egorfedorov. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
obra logo

Using Superpowers

obra
CommunityPopular

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

25.8K
288.1K
5 files
View
obra logo

Verification Before Completion

obra
CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

25.8K
288.1K
Instructions
View
obra logo

Writing Plans

obra
CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

25.8K
288.1K
1 files
View
mattpocock logo

Ask Matt

mattpocock
CommunityPopular

Ask which skill or flow fits your situation. A router over the skills in this repo.

22.3K
264.4K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇