mozg.betaSign in

explore / Game development / mozg / Stake Engine

Stake Engine · Web SDK

Answer questions about building the game frontend with the Web SDK: the file structure of a game, how context and state are shared, how events from the maths are consumed and animated, the UI components provided, and how Storybook is used to develop them.

185 notes · updated 2026-08-04 · trained 66%

since last sitting: +1 newly passed — this brain is learning

Ask it things like

answers 19/30 on its latest exam
Which Svelte contexts does a Web SDK game rely on, and which package provides each?Context and state✓
Trace what happens from the moment the RGS response arrives until a component animates something.Events and maths integration✓
Give me the ordered checklist for adding a brand-new bookEvent to an existing game.Events and maths integration✓
What is the difference between broadcast and broadcastAsync, and when do I need each?Events and maths integration✓
What story namespaces exist per game mode, and which story do I use for a final end-to-end check?Storybook✓
Write me a story that exercises a single bookEvent, and tell me where the event data comes from.Storybook✓
Why does the SDK use xstate for game flow, and how do I disable the bet button while a spin is running?Context and state✓
How does a component know the canvas size, and how do I pin a sprite to the left or right edge of the canvas?Context and state✓
use this brain
# sign in to get a token
$ claude mcp add --transport http mozg \
https://mozg.sh/mcp --header "Authorization: Bearer …"
> use mozg/stake-engine-web-sdk — …
Get a token

Use this brain

Sign in and add it, and every agent you have connected can read it — nothing to download, and it stays current as the author updates it.

Sign in to add it

What it can answer

30 checks
66%
▲Context and state5 / 6
▲Events and maths integration5 / 7
▲Storybook5 / 6
▲Project setup & file structure2 / 4
▲UI components & animation2 / 6
✕RGS wiring, build & testing0 / 1
exam badge — share this score →

Inside

  • Task Breakdown principle for emitterEvents · events and maths integration
  • Testing atomic emitterEvents in Storybook · storybook
  • emitterEvent subscription in TumbleBoard component · events and maths integration
  • Stateless vs Stateful games definition · events and maths integration
  • emitterEvents from different Svelte components under one bookEvent · events and maths integration
  • tumbleBoard task breakdown example · events and maths integration
  • bookEventHandlerMap tumbleBoard implementation · events and maths integration
  • UI component import from components-ui-pixi · ui components
  • UI components from components-ui-html · ui components
  • GameVersion component usage · ui components
  • UI components are starter examples, not production-ready · ui components
  • UI component snippet API · ui components
  • UI component packages provided by SDK · ui components
  • UiGameName component usage · ui components

Licence

CC BY-NC-SA 4.0

Use it, copy it, build on it, with credit. Selling it is not allowed.