Game Builder Overview
Design complete games through conversational AI — from elevator pitch to asset prompt tree.
Game Builder Overview
The Game Builder transforms the SpriteSynth MCP into a Game Pre-Production Studio. Instead of generating random assets one at a time, you work through a conversational design funnel that produces a complete game design repository — including a game bible, asset dependency graph, and AI generation prompts for every single asset your game needs.
This is not an AI asset generator. It is an AI game producer, art director, and content planner that ensures creative consistency and scope control before any assets are generated.
Why the Game Builder?
Most AI game generation workflows look like:
"Generate a platformer."
Which produces a random collection of code, sprites, sounds, and mechanics that don't fit together.
The Game Builder solves three core problems:
| Problem | Solution |
|---|---|
| Creative consistency | Style DNA + locked creative direction ensures all assets share the same visual language |
| Scope management | Config-driven scope limits cap enemies, biomes, NPCs, and items to match your team size and timeframe |
| Asset planning | Recursive asset discovery ensures nothing is forgotten — every mechanic triggers its required asset set |
How It Works
The Game Builder uses a progressive design funnel with 5 stages. Each stage builds on the previous one:
Vision → Scope → Bible → Assets → ReviewStage 1: Vision
Define the core concept of your game:
- Elevator pitch: One-sentence description
- Genre: Single genre or genre-mix (e.g. "farming-sim + roguelike")
- Comparable games: Reference games with specific aspects to emulate
- Story & Theme: Narrative premise and core mood
The MCP asks you one question at a time, building up a structured game design document.
Stage 2: Scope
Set realistic constraints before planning details:
- Team size: solo, small, medium, large
- Timeframe: weekend, month, quarter, year
- Quality target: prototype, indie, steam-quality
The system then estimates realistic caps: max_enemy_types: 8, max_biomes: 3, max_npcs: 15 — actively preventing scope creep.
Stage 3: Design Bible
Generate a complete design bible covering:
- Core gameplay loop
- Progression and economy systems
- Combat mechanics
- Narrative structure
- Controls and UX principles
Creative direction can be locked at this stage, preventing future design drift.
Stage 4: Asset Planning
The system recursively discovers every asset your game needs:
- Canonical taxonomy: Config-defined minimum asset sets per genre
- Mechanic discovery: Additional assets triggered by features like fishing, crafting, mounts, etc.
- Dependency graph: Relationships between assets (characters → animations → tilesets)
- Asset prompts: AI generation prompts pre-filled with style DNA for consistency
- Budget estimation: Total asset count by category with risk factors
Stage 5: Review & Export
A multi-criteria review scores your design:
| Criteria | Weight | What It Checks |
|---|---|---|
| Fun | 30% | Core loop engagement, player agency, reward pacing |
| Cohesion | 25% | Art-mechanic fit, narrative-theme alignment |
| Scope Risk | 25% | Asset count vs team/time, feature creep |
| Market Fit | 20% | Genre conventions, unique hook clarity |
The result is a ship probability and specific recommendations.
Finally, the system exports a complete design repository:
/game/{title}/
GAME_BIBLE.md
VISION.md
SCOPE.md
design/core-loop.md
design/progression.md
design/combat.md
art/STYLE_DNA.md
art/creative-direction.md
assets/ASSET_MANIFEST.md
assets/asset-budget.md
assets/asset-prompts/{category}/{asset}.md
meta/game_genome.json
meta/dependency_graph.json
meta/scope_report.jsonQuick Start
In a single conversation with Claude or Cursor:
1. "Let's design a game. I want a creature-collector metroidvania."
2. "Stardew Valley meets Hades with Pokemon-style creature collecting."
3. "Solo dev, one year, indie quality."
4. "Pixel art, adventurous tone."The MCP guides you through each stage, calling the appropriate tools and storing the design in your account.
Advanced Features
Beyond the core 5 stages, the Game Builder includes:
- Style DNA extraction: Structured visual analysis from reference games (perspective, saturation, contrast, shape language, color script)
- Art direction bible: Shape languages for hero/villain/neutral, color scripts per game phase, palette suggestions
- Scope compression: Analyzes ideal vs realistic scope and recommends cuts
- Vertical slice planning: Minimum 30-minute playable demo plan with P0/P1/P2 priority tiers
- Coding context packs: Spec, schema, test, and UI documentation for every game system
- Design health checks: CI/CD-style checks across scope, fun, lore, balance, and art consistency
- Competitive positioning: Steam tags, market gap analysis, competitor identification
See the Game Builder Workflow guide for a complete walkthrough, or the Tools Reference for detailed parameter documentation.
Note
The Game Builder is a design and planning tool. It produces a complete game design document and asset prompt tree. You then use the standard generation tools to create the actual assets, or export the design repository to feed into AI coding agents.