explore / Game development / egorfdrv

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.

108 notes · updated 2026-08-03 · trained 49%

use this brain

# sign in to get a token

$ claude mcp add --transport http mozg \

https://mozg.sh/mcp --header "Authorization: Bearer …"

> use egorfdrv/stake-engine-web-sdk — …

Get a token

What it can answer

30 checks

49^%

▲Storybook5 / 6

▲Context and state3 / 6

▲Events and maths integration3 / 7

▲UI components & animation2 / 6

▲Project setup & file structure1 / 4

✕RGS wiring, build & testing0 / 1

Inside

Example: composing UI inside App with gameName and logo snippets · UI components
Logo snippet uses a Pixi Text with REM-based font sizes · UI components
UI Components docs page position · Documentation navigation
Treat the provided UI packages as a starting point, not the final product · UI components
UI packages: components-ui-pixi and components-ui-html · UI components
Task Breakdown doc page metadata · Documentation navigation
emitterEvent colors indicate different svelte components · Events and maths integration
Splitting tumbleBoard bookEvent into atomic emitterEvents · Events and maths integration
subscribeOnMount in TumbleBoard.svelte · Events and maths integration
Task Breakdown principle in carrot-game-sdk · Events and maths integration
Testing broken-down emitterEvents in Storybook · Storybook
bookEventHandlerMap tumbleBoard handler example · Events and maths integration
Stateless vs stateful games · Web SDK overview
bookEvent stories such as MODE_BASE/bookEvent/reveal · Storybook

Licence

CC BY-NC-SA 4.0

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