← the studio
A desktop game-scaffolding tool

Vibe Engine

Describe the game you want. Vibe Engine interviews you, distills the answers into a structured game design document, and scaffolds a playable Unreal Engine 5 project from it — terrain, AI, modes, HUD, menus, audio, and post-process.

From a conversation to a playable level.

What it does

An interview becomes an Unreal project.

The blank-project problem is brutal: you know the vibe long before you know the hundred settings that produce it. Vibe Engine closes that gap — it asks about your game, turns the conversation into a GDD as structured JSON, then drives the Unreal Editor's Python API to generate a project that boots to a menu, loads a level, and plays.

Watch it build

Interview → design doc → a scaffolded, playable project.
vibe-engine · scaffoldinterviewing…
interview
→
GDD (JSON)
→
scaffold (UE5)
→
playable
terrain + props AI: patrol · boss · swarm game mode HUD + menus music state machine post-process
Genre sets the base, tone modifies it, art direction overrides specifics — so every module traces back to the GDD, the design doc the interview produced. Boots to a main menu → loads Level_1 → plays.

What it generates

A whole vertical slice, wired up.

Terrain & props

A level with terrain and placed props, ready to walk through.

AI archetypes

Patrol (guard), Boss, and Swarm — each with its own behavior tree.

Mode, HUD & menus

A main menu that launches the level, a HUD, and the rules that make it a game.

Audio & post-process

A music state machine (Menu → Explore ↔ Combat → Boss → Victory) and a genre-driven look.

The contract — and the honest limit

The GDD is the spec; "fun" isn't gate-checkable.

Vibe Engine keeps the studio's Explain move — the structured GDD is the contract, and everything the scaffolder builds traces back to it, so the project is a faithful read of what you described, not a random template. Built as an Electron shell with Claude running the interview and UE5's Python API as the body.

Where it parts from the thesis: there's no deterministic Verify gate here, because "is this game good / fun" isn't something Python can score. It guarantees faithfulness to the GDD — a real, working starting point — not that the result is a great game. That last mile is yours.