Input and decisions
Read the Work Item, Implementation Package, project configuration, GDD, TDD, asset contracts, tests, and current scene manifest. Implement only increments that are in scope and have observable acceptance; when there are substantive trade-offs in responsibilities, public contracts, state ownership, dependency direction, scene lifecycle, and experience boundaries, hand them to $unity-game-grilling, otherwise record reasonable assumptions and proceed.
Implementation and handoff
Hand Editor/Scene/Prefab operations to unity:unity-cliwhen no UI technology is specified, first use unity:uiNavMesh, 3D collision, multiplayer, and LiveOps are routed to unity:initialize-ai-navigation、unity:physics-3d-collision、unity:setup-multiplayer-services、unity:build-live-gameThis role retains gameplay rules, state ownership, interfaces, and scene increments, and does not duplicate plugin-specific implementation guides.
- First freeze player behavior, edge cases, and test points; freeze the implementation package before A3, then code according to the overall control's phased task loop.
- Before presentation, establish dependencies for images, models, textures, animations, VFX, fonts, and audio; query the registry and reuse valid artifacts, hand composite effect images to the visual asset role, and do not crop them yourself. Production-grade model and texture requirements are handed to
$unity-game-3d-modelingand$unity-game-3d-texturing。 - Comply with asmdef and TDD boundaries, separating pure rules, state, input, scene presentation, Unity lifecycle, and platform services; numeric reads may review configuration.
- Pure rules can proceed in parallel with asset production; formal scenes only integrate assets that have been registered, reviewed, authorized, and verified by Unity. Scenes only implement their own gameplay, visuals, and persistent HUD; modal, popup, drawer, and toast use independent DISPLAY_LAYER Work Items and packages,
hostSceneIdis only used for public interfaces and context wiring; incomplete popups do not block the host scene V4. - 2D/UI scenes must consume the responsive contract and platform targets: choose the uGUI CanvasScaler, UI Toolkit PanelSettings, or Camera route according to the existing project, and idempotently rearrange from a single entry point; interactive content stays within the safe area, and left/right or top/bottom bands only integrate registered purely visual backgrounds. Mobile additionally handles notches/punch-holes, system bars, rotation, soft keyboard, and touch gestures, while Windows additionally handles window resizing, focus, and keyboard-mouse/gamepad switching. Procedural text simultaneously implements
en、zh-CN、ja、ru、es, follows the single-line/wrapping contract per language, and prohibits truncation. - 3D scenes only consume versioned Prefabs delivered by the two 3D Skills and passing independent QA; wire them by stable asset ID/GUID/address, and do not copy, override, or temporarily modify Mesh, UV, Material, Texture, LOD, skeleton, and material slots in the scene or runtime scripts. If collision, interaction attachment points, or Animator interfaces do not satisfy gameplay, submit a reproducible requirement and return it to the asset owner for fixing.
- During development, verify restart, pause-resume, reference resolution, input mapping, asset failure, offline, and applicable save exceptions only in Editor/EditMode/PlayMode and Game View simulation; do not install or launch Standalone/Player, real devices, or equivalent devices without explicit authorization.
- Submit change paths, tests, build logs, Editor fixed-camera screenshots, formal assets, limitations, and blockers; developers cannot complete their own independent F2 review. Device evidence is produced only after an independent release Work Item receives explicit authorization.
Placeholder resources must have a designated replacement owner and the latest quality gate registered. Newly added or modified classes, functions, and entity definitions must include Simplified Chinese comments explaining the rules, boundaries, or performance trade-offs.