SuperAPI AI Directory

unity-development-workflow

Coding & development

View repository

Updated 10-16 08:49

About this skill

Unity game development orchestration

With unity-game-workflow-control as the sole global state, risk gate, task scope, and evidence authority. This Skill is responsible for Unity domain decomposition, handoff artifact freezing, Editor write orchestration, and evidence convergence; it does not maintain a second state machine, nor does it approve side-effectful operations on the user's behalf.

Shortest process

  1. Read the Work Item, current phase, project baseline, and applicable gates; first followUnity plugin capability routingto select the plugin Skill, then read as neededWorkflow overview、@Unity execution contract、Project discovery、Module planning、Responsive UI contract、Screen UI layout and node tree、TMP multilingual font atlas、Game implementationandDelivery。
  2. Show project progress as "requirements and scope → global baseline → foundational project → scene and popup production → global integration verification → release." A purely local task establishes only one Work Item and lands directly on the earliest affected phase, without being forced to redo unrelated phases.
  3. Before A3 production implementation, freeze the Implementation Package, specifying the baseline, file ownership, Unity object ownership, execution units, verification commands, and stop conditions. When the intra-task plan, paths, or asset manifest change, update the package and re-verify the affected scope.
  4. After implementation, record candidate diffs, recommend a T0-T3 test level, and then execute automatically; for evidence failures, prioritize fixing in place repair, and when upstream facts are unchanged revalidate, rerun only when upstream is invalidated, the scope has truly changed, or a hard gate would otherwise be bypassed return。
  5. After the phase is complete, return to the control plane and run check/run. External writes, payments, real devices, destructive deletion, signing, uploads, and releases must have precise object approval established by the control plane.

Unity native execution constraints

  • When establishing a project for the first time, planning modules, or adding directories, comply withproject structure constraints, and keep directory mapping, asmdefs, scene lifecycle, and ownership consistent in the TDD and implementation package.
  • Before writing in Unity, discover the instance, bind a unique Editor by normalized project path, and wait for import, compilation, and domain reload to stabilize; after writing, re-read the target objects, Console, Scene/Prefab, Importer, GUIDs, and registration results. Before switching scenes and other commands that may trigger a save prompt, first followscene save pre-checkcheck only the scenes modified by the current task, and save via the Unity scene save command.
  • Assets/ Files managed by Unity in and .meta are treated as a single ownership unit. It is forbidden to generate or guess GUIDs outside AssetDatabase; prioritize using Unity APIs to move/rename assets to avoid broken references.
  • ProjectSettings/、Packages/, Build Settings, Addressables global configuration, shared asmdefs, and cross-scene entry points may only be modified serially. Formal Editor writes to the same physical Unity project must remain single-writer.
  • Runtime assemblies must not reference Editor assemblies; modifications to Scene, Prefab, ScriptableObject, and UXML/USS must be saved and serialized references re-verified after domain reload.
  • R&D verification prioritizes EditMode, PlayMode, Game View, static budgets, and device-free builds. Without explicit user request, do not launch Standalone/Player or real devices; release actions are also not automatically approved just because a build succeeds.

Scene V0-V4

Each SCENE and DISPLAY_LAYER 's V0–V4 all followstage manual confirmationsubmit viewable artifacts stage by stage, and only proceed to the next stage after obtaining explicit user confirmation; only close after V4 confirmation.stageReviews bind work items, baselines, and delivery summaries; technical PASS, initial authorization, or silence cannot replace manual confirmation.

Scenes close the loop by V0 分流 → V1 场景定义 → V2 拆解确认 → V3 正式资源与组合验收 → V4 正式实现与运行验收 . Visual tasks readVisual WorkflowandScene Closed Loop。

  • V1 freezes the gameplay contract, Scene/Prefab/UI structure, stable node IDs, host context, responsive layout, safe area, multilingual text strategy, and acceptance trajectory.
  • V2 first freezes node responsibilities, actual hierarchy dependencies, semantic grouping, and layout contract, then separately freezes visual sources and Scene/Prefab/UI assembly; at the same time record component states, Importer/GUID/address conventions, and visual boundaries that users must decide. Screen UI usesNode Tree and Component Grouping Rules。
  • V3 verifies final assets, Prefab/Scene/UXML combinations, serialized references, and same-screen effects in the host; graybox or full mockup images must not be passed off as final assets.
  • V4 completes final integration, interaction trajectory, cleanup, Console, responsive, and performance evidence in Editor/PlayMode. A scene only closes the loop for its own visuals and persistent HUD; modal, popup, drawer, and toast establish independent DISPLAY_LAYER Work Items and Implementation Packages, whose hostSceneId only indicates context; if incomplete, it does not block the host scene V4.

Domain Collaboration

Art, architecture, gameplay, visual, 3D, audio, numerical, QA, and release Skills only submit domain proposals, implementation results, or evidence. When existing Spine characters are only reskinned, call $unity-game-spine-reskin. Developers must not review their own deliverables; F2 domain quality review and F3 engineering verification are recorded separately. For parallel rules, seeMulti-Agent Execution。

Tool Entry Points

Project documents and JSON Jobs are still handled by minimal file tools; control state is handled by unity-game-workflow-control , and Unity facts are handled by @Unity、com.unity.pipeline and the accompanying Toolkit:

node .\.agents\skills\unity-development-workflow\scripts\workflow-files.mjs init-docs --project-root D:\Projects\my-game --project-id my-game
node .\.agents\skills\unity-game-workflow-control\scripts\workflow-control.mjs status --repo D:\Projects\my-game --work-item D:\Projects\my-game\.workflow-control\work-items\current.json

Unity commands are not repeated in this Skill; when executing, read the matching Unity plugin Skill. Neither Node nor desktop clicks can replace Unity's factual verification of Scene, Prefab, Importer, AssetDatabase, compilation, tests, or builds. Unless the user explicitly requests it, do not create worktrees or branches, and do not sign, upload, release, or initiate real-device acceptance.