Establish maintainable, testable, buildable technical boundaries, and let S00 carry only the global skeleton with proven reuse evidence.
Input and decisions
Read the Work Item, project configuration, GDD, TDD, module manifest, and code facts. When there are substantive trade-offs regarding technical direction, public interfaces, save migration, package dependencies, performance budgets, or distribution methods that cannot be reasonably inferred, hand them to $unity-game-grilling; ordinary first-time implementations or reversible local architecture choices are advanced by the implementation package after recording reasonable assumptions.
Execution and handoff
When first establishing the project, planning directories, or reviewing module boundaries, readproject structure constraints, and fix the directory mapping, assembly dependencies, scene lifecycle, and asset ownership in the TDD; subsequent new implementations must follow this contract.
Project creation and Editor/build operations are handed to unity:new-unity-project、unity:unity-cli; UPM is handed to unity:unity-package-management; BiRP→URP and Render Graph specializations are handed to unity:migrate-birp-to-urp、unity:validate-urp-render-graph-renderer-featurerespectively. This role only decides architecture, budgets, dependencies, and acceptance boundaries, and does not repeatedly maintain plugin operation steps.
- Record in the TDD the Unity Editor, Unity CLI,
com.unity.pipelineand package versions, module responsibilities, asmdef, Composition Root, scene and state flow, input, time/random, assets, save data, logging, error handling, testing, and builds. - Separate pure rules, Unity presentation, Editor tools, and external services; Runtime assemblies do not reference Editor implementations.
- Only move capabilities needed by at least two scenes up to Foundation/Shared; establish a consumer and change impact list for public interfaces.
- In the foundational engineering phase, implement a runnable minimal skeleton, test entry points, and a reproducible empty-shell build as SHARED/MODULE units; platform services are isolated through interfaces, and no implementations are added for unselected platforms.
- Define a unique Unity-native responsive contract for all visible Scenes, persistent HUDs, and independent DISPLAY_LAYERs, freezing Camera, Screen/Game View, CanvasScaler or PanelSettings, safe area, input coordinates, resize/orientation, text, asset resolution, performance budgets, and representative viewports. UI/2D bitmaps default to
sourceScale=1only indicates production pixel density, not a fixed runtime DPR; runtime is based on the platform, Canvas/Panel, Camera, Render Scale, dynamic resolution, and Importer measurements. - The scene Implementation Package contains only
SCENE, the popup package contains onlyDISPLAY_LAYER;hostSceneIdonly binds public interfaces and runtime context, and does not indicate ownership or completion dependencies. Scene/Prefab/UXML/UIDocument assembly and visual asset sources are modeled separately; using full-screen composite images instead of structure is prohibited. - Define verifiable budgets for 3D assets based on target devices, camera distance, and scene density: triangles/vertices, LOD, bones and skinning, material slots, colliders, Texel Density, texture size and memory, Mip/Streaming, Draw Calls, Shader/variants, and Prefab dependencies; hand the budgets to
$unity-game-3d-modeling、$unity-game-3d-texturingand independent QA respectively, and do not replace them in producing or approving assets. - Specify the 3D runtime directory, stable asset IDs, model/material/Prefab ownership, and replacement boundaries; gameplay may only consume registered and verified Prefabs, and duplicating and privately modifying Mesh, Material, or Texture within a scene is prohibited.
- Unity writes according to
unity:unity-clidiscovers the unique project target and actual commands based on the current rules; the results must still be backfilled into the current implementation package and evidence list.
Newly added or modified classes, functions, and entity definitions must have Simplified Chinese comments; the comments shall explain design boundaries, lifecycle, compatibility risks, or performance trade-offs.