UniKit AI

The AI Development Pipeline for Games: design, code, and the engine editor

Building a game with AI usually breaks in the same place: the agent writes a class, and then stops. The design lives in someone's head, the scene lives in the editor, and neither is something a prompt can reach. UniKit AI closes that gap - it authors the game design, plans and writes the code against a memory of your engine and stack, and carries the same plan into the engine editor through the engine's MCP server. An engineered pipeline instead of vibe-coded prompts.

Why UniKit AI?

• Spec-driven development cycle - explore the idea, plan, implement, review, verify, document. Each step reads the artifact the previous one wrote: no prompt engineering, no re-explaining the project every session, and a plan you can read and correct before a line is written. Predictable enough that a small model can execute a plan a large one made
• Almost the whole cycle, not just the code - design the game, write the code, work in the editor. One pipeline covers all three, and a single plan can mix code tasks with editor tasks
• The engine MCP is used to the full, and checked - the agent gets real-time feedback from the running editor: console, compilation errors, test runs, editor state. Every result is read back from the editor rather than taken from the server's response
• Framework rules out of the box - ready-made rules for engine modules and popular frameworks from the official registry. Plug in your own Git registry to carry a private rule library across projects, or generate fresh rules from your codebase on the fly
• Dynamic memory - one memory for all engine frameworks instead of a separate skill per library. Core rules are always loaded, stack rules are pulled in by task context - saving tokens and keeping the context window lean
• Self-learning memory - the agent turns bug fixes and code reviews into patches, then distills them into improved project rules. The system gets smarter with every fix

Scope

UniKit AI covers three layers of game development:

Layer	What it covers
Game design	concept, pillars, systems, flows, content schemas - a machine-readable design that code plans read from
Game code	architecture, systems, tests, refactoring, review, documentation
Engine editor	scenes, prefabs, UI, materials, animation, assets, project settings - planned as explicit tasks, executed through the engine MCP

Editor work is a first-class part of a plan, not an afterthought: it is planned next to the code, carried out through the engine MCP and verified by reading the result back from the editor. See Editor tasks.

Art production, audio authoring, and store/build pipelines are not covered.

Supported Engines