⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
unikit
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
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
Each engine ships one or more MCP servers. Where several are listed, they are alternatives - unikit-ai init offers them as a choice and the first one is the default. The versions are each vendor's own minimum, and UniKit AI does not detect your engine version, so check yours before accepting the default.
| Engine | MCP servers (in wizard order) |
|---|---|
| Unity | Unity Biome MCP (Unity 6000.0+) · Coplay Unity MCP (Unity 2021.3 LTS+) |
| Godot 4 / Godot 4 .NET | Fennara Godot AI - free (Godot 4.5+) · GDAI Godot MCP - paid (Godot 4.1+) · Coding-Solo Godot MCP - free (no declared minimum) |
| Unreal Engine 5 | ChiR24 Unreal MCP (Unreal Engine 5.0+) |
See Configuration for how UniKit AI works with each server.
Supported Agents
| Agent | Config Directory | MCP Support |
|---|---|---|
| Claude Code | .claude/ | Yes (.mcp.json) |
| Codex CLI | .codex/ | Yes (.codex/config.toml) |
| Cursor | .cursor/ | Yes (.cursor/mcp.json) |
| Qwen Code | .qwen/ | Yes (.qwen/settings.json) |
| OpenCode | .opencode/ | Yes (opencode.json) |
| Antigravity | .agents/ | Yes (.agents/mcp_config.json) |
| Kimi Code | .kimi-code/ | Yes (.kimi-code/mcp.json) |
| Universal / Other | .agents/ | Yes (.mcp.json) |
Select one or more during unikit-ai init. See Agents for agent-specific caveats.
Installation & Quick Start
npm install -g unikit-ai # install
unikit-ai update # later: reinstall only what changed in the project
unikit-ai init # in your game project directory
The wizard asks which AI agent you use and which game engine, configures the MCP servers, and installs the skills, subagents and engine templates.
Context7 is also recommended - the agent uses it for generating framework rules and deep research of libraries and APIs.
Then open your AI agent and start working:
/unikit
/unikit scans your game project, detects the full tech stack, asks targeted questions to fill in gaps, generates project description
// HOW IT'S BUILT
KEY FILES