// AI GAME DEVELOPMENT

YetiClaw Studio: 27 Agents That Build Games

May 21, 2026 · Yeti Games, LLC · 10 min read

YetiClaw Studio is a self-hosted AI game development system — 27 specialized agents covering every role in a real game studio, from producer to QA tester, running on local hardware with no cloud subscription required. We used it to ship Zeal's Dark Alchemy — a browser-based RPG on VIVERSE — from blank brief to deployed game.

This is a breakdown of the architecture: how the agents are structured, how they collaborate, and how a project brief becomes a shipped game.

The Stack

Config: 32,768 max tokens, temp 0.7, subturn depth limit 3, token budgeting on, sensitive data filtering active. Local gateway on port 18789 (Orange Pi) or 3002 (Mac).

The 27 Agents

Each agent is a skill module — a SKILL.md file defining role, responsibilities, collaboration protocol, and execution rules. Agents maintain max_history: 5 for memory management across long sessions.

How a Game Gets Built

1. The Producer Creates the Brief

Every project starts with one command:

/producer set up a new project brief for:
  Zeal's Dark Alchemy,
  dark RPG,
  VIVERSE (browser),
  Three.js + WebXR,
  alchemy crafting loop,
  gothic atmospheric

The Producer writes the full brief in plain text — no agent spawning — and saves it to:

gdrive:YetiClaw/gamedev/zeals-dark-alchemy/brief.md

The brief format: name, tagline, concept, core loop, platform, controls, engine/tech, visual style, 5 key mechanics, target audience, monetization, timeline, budget. Every other agent references this file by project name. It's the single source of truth that keeps 27 agents consistent across the full development cycle.

2. Specialists Expand Each Section

After the brief exists, specialists are called by section:

/gamedesigner using the Zeal's Dark Alchemy brief, design the alchemy crafting system
/gameplay-programmer using the brief, implement the potion brewing mechanic in Three.js
/sound-designer using the brief, spec the procedural gothic soundtrack

Each agent follows a structured protocol before writing anything: ASK for missing context → present OPTIONS → WAIT for approval → DRAFT output → REQUEST write permission. No agent writes files without an explicit approval checkpoint.

3. The Collaboration Model

Agents don't operate in isolation. The Game Designer consults the Technical Director on architecture before finalizing mechanics. The Art Director and Sound Designer sync on tone. The QA Tester gets the Game Designer's spec before writing test plans. These cross-functional checkpoints are baked into each skill's protocol — not enforced by the orchestration layer.

Paid API calls (Meshy 3D generation, Nano Banana 2 image gen) go through approval gates. The Asset Approver agent reviews every Meshy request before execution — cost control built into the workflow.

4. Local-First, Cloud-Optional

The entire system runs offline. Qwen handles reasoning, code generation, design documents, dialogue, and QA planning without touching a paid API. Cloud integrations (Meshy, image gen, Google Drive sync) are opt-in and gated. A full game development session on a $200 ARM board costs nothing beyond the initial hardware.

What the Game Designer Agent Actually Produces

The Game Designer writes 8-section GDDs applying the MDA Framework (Mechanics → Dynamics → Aesthetics) and validates against Bartle Player Types (Achiever, Explorer, Socializer, Killer). For Zeal, that produced:

• Alchemy crafting loop: ingredient discovery → recipe experimentation → potion execution
• Cursed run variations: each playthrough modifies the ingredient set, keeping exploration fresh
• Transformation sequences: visual feedback tied to potion quality tiers
• Progression system: knowledge accumulation as the core unlock loop, not gear or levels

What the Gameplay Programmer Agent Produces

For Unity projects: Unity 6 LTS, C#, ScriptableObjects for tuning, delta time calculations, PascalCase classes/methods, _camelCase private fields, XML doc comments, null-checking required, zero TODOs in production code. For VIVERSE: Three.js + WebXR, browser-native, deployed via the VIVERSE platform.

The programmer agent confirms specs, outlines architecture, waits for approval, then drafts code — same approval-gate pattern as every other agent.

Deploying to VIVERSE

VIVERSE is HTC's browser-based social XR platform. Games run in WebGL/WebXR — no install, no app store. The Three.js Dev agent handles the platform integration: scene setup, asset loading, controls for both desktop and VR headsets, and the VIVERSE SDK hooks for multiplayer presence.

Zeal's Dark Alchemy is live on VIVERSE at viverse.com/8ovBnhx. Read the full case study →

The Open-Source System

YetiClaw Studio is MIT-licensed and publicly available. The repo includes all 27 skill modules in two variants — skills/ (Orange Pi ARM64 optimized) and skills-mac/ (Mac/Windows optimized) — plus deployment scripts, config, and the full workflow documentation.

If you want to deploy your own AI game studio on local hardware, the full setup is in the repo. If you want a team to build something for you using this system, that's what we do →