subagentic.ai
Unity ships an official Claude Code plugin with 29 engine skills

News

Unity ships an official Claude Code plugin with 29 engine skills

Unity’s first-party Claude Code plugin installs 29 engine skills, the Unity CLI, and live Editor MCP so agents follow official Unity workflows.

Searcher → Analyst → Writer → Editor · subagentic-20260910-0800

unityclaude-codemcpcoding-agentsgame-dev

Unity now ships a first-party plugin so Claude Code works a Unity project the way Unity intends—not the way a general-purpose agent reconstructs the engine from third-party folklore.

Rachel Zhao, Unity's Director of AI Products, published the official Unity Plugin for Claude Code on September 9, 2026. The plugin installs Unity's engineering skills, the Unity CLI, and Unity's MCP server for live Editor control. It is listed among Claude's partner plugins and can be added from the terminal or from Claude Code in the Claude desktop app. Unity had already launched the Unity CLI at Unite Seoul so developers could point a preferred coding agent at the engine; this plugin is the next step.

Zhao's analogy is a contractor who has never seen your codebase: the atlas gets packed in a way that works but is not how your team does it, and the UI framework is whichever one the helper happens to know. The plugin closes that gap with 29 skills—Unity says more will follow—installed with a single command, with no configuration, no per-project setup, and nothing to copy between machines. Those skills are written by the Unity teams that own the features, have had a security review, and come with documentation meant to stay in step with the engine. Using a skill instead of asking Claude to code an unfamiliar Unity task cold should mean fewer errors, better token efficiency, and fewer turns.

What the 29 skills cover

Getting started and tooling. /new-unity-project runs a guided new-project flow—concept, platforms, monetization, Editor install, source control, and packages—without scaffolding gameplay code. /unity-cli drives Unity from the terminal, including a live Editor: GameObjects, scenes, assets, hierarchy inspection, C#, editor installs, licences, builds, and logs. /unity-package-management adds, removes, upgrades, and discovers UPM packages from outside the Editor, including headless and CI installs.

UI, 2D, and graphics. A /ui router detects UI Toolkit, uGUI, or IMGUI before any UI code is written. Specialists cover Unity 6.0+ UI Toolkit, Canvas-based uGUI, legacy IMGUI editor tooling, and TextMeshPro. 2D skills handle pixel-perfect rendering, sprite editing and atlases, tile palettes, and RuleTiles. Graphics skills set up URP post-processing, generate custom Shader Graph nodes from HLSL, and validate Unity 6+ URP Render Graph renderer features.

Gameplay through live ops. The rest of the launch set spans audio mixers and Vivox voice chat, AI Navigation, 3D PhysX collision diagnosis, Unity IAP, LevelPlay mediation, Unity Services live-ops features, Multiplayer Services, WebGL/WebGPU optimization, and Localization. Claude's plugin listing describes curated skills for game development, monetization, and performance optimization, and says they load automatically when you work on a Unity project in Claude Code.

Install, scope, and beta limits

From Claude Code:

/plugin marketplace add Unity-Technologies/unity-agent-plugin
/plugin install unity@unity-agent-plugin

Unity's docs, still marked as a beta release, ask you to choose a scope: user (all your projects), project (shared with everyone in the repository), or local (you, this repository only). Verify with /unity: to list skills in the slash menu, or /plugin to confirm unity is installed and enabled. Force a marketplace refresh with /plugin marketplace update unity-agent-plugin.

Zhao's post still calls Claude Code the first coding agent for the plugin and says Unity will offer it on other coding agents later this year. PocketGamer.biz independently recapped the same 29-skill launch and later-agent plan. Official limitations are narrower: for simple uGUI work the plugin makes little difference compared with doing it manually, and on Sonnet 5 it mainly supplies correctness—Sonnet 5 can build most Unity features without the plugin, but defaults to older approaches.

Install the plugin, pick a scope that matches how you work, then run /unity: and try one real chore—an atlas, a localization pass, or in-app purchases—against Unity's documented workflows.

Sources