How it cooks.

Getting started

1. Open the demo. /p/demo is the whole studio with Neon Koi already cooked — every stage, Kiko's mascot pipeline, the timeline and the HUD builder. Poke at anything; nothing is saved and nothing costs a credit.
2. Pick a plan. Your own games start with a plan (from $99/month, 8,000 credits every month). There's no trial — the demo is the trial. See pricing.
3. Cook a Slot. In your kitchen, press Cook a Slot: name, the idea in a sentence, how it pays, the grid, RTP, max win, volatility and the bonuses. Creating a game is free and it's playable at once.
4. Let the Chef cook. Press / in the studio and ask, or connect your own Claude Code over MCP (guide). Every step lands in the studio as it happens. Want the mascot rigged in your own Spine? See the animation toolkit.

The four kitchens

A game is a Recipe — one document the studio, the Chef and your Claude Code all edit. The stages are grouped into kitchens; each chip in the studio's top bar shows whether its stage is not started, working, waiting for review, done or blocked.

• Recipe — Recipe (title, tagline, theme + palette)
• Math Kitchen — Math (paytable, board weights, modes) · Bonuses (modules, their math, HUD and timeline sections)
• Art Kitchen — Art (symbols, wild, scatter) · Mascot (Spine 4.2 skeleton, atlas, pages) · Sound (18-cue SFX board, music bed base, music bed bonus)
• Game Kitchen — Motion (default scenes, win tier choreography) · HUD (web 1200×675 layout, mobile 420×900 layout, skin) · Serve (math books, Stake zip, check report)

Studio tour

The canvas in the middle has five modes — Scene (the game playing a real outcome), Inspect (one symbol, asset or the Spine mascot with its bones and animations), HUD (the builder, on web 1200×675 and mobile 420×900, checked on all ten Stake viewports), Math (the sim: RTP, hit rate, the win distribution) and Pipeline (every stage as a card). The left panel holds the Recipe, Math Kitchen, bonuses, assets, the HUD and the Chef. The timeline at the bottom is the choreography: sections from idle to epic win, tracks for reels, symbols, the mascot, FX, text and sound, played from a real math book.

Keys worth knowing

Press ? in the studio for all of them. No shortcut ever spends credits.

Credits

Editing is free: the Recipe, the HUD, the timeline, bonus toggles and live sims within your plan's daily spins. Credits pay for what our servers generate — art, the mascot, sound, production math books and the Stake zip — and for Ask Chef turns in the studio (metered by the model's real usage). Over MCP, your own Claude Code does the thinking on your Claude plan.

Every paid control shows its price before you press it. The kitchen holds the credits first; if your plan is off or the balance is short, nothing runs and nothing is charged — you get the exact reason and one button to fix it. Plan credits arrive every 30 days and reset at the end of the cycle; packs never expire.

Serve to Stake

The Game Kitchen's last stage, Serve, builds the math books for every bet mode (darkbyte-mathcore: books, lookup tables and index — the same files Stake Engine reads) and the front, runs the gates — math compliance, HUD lint on the ten viewports, the choreography review — and zips it all. Red gates release the credits and tell you what to fix.

You upload the zip with your own Stake Engine account; we never ask for your session. Games served from Starter and Pro show a small “Cooked on slot.cooking” badge on the loading screen; Studio is white-label.