unity-project-setup

# Unity Project Setup Prepare a connected Unity project for reliable feature work without hand-editing serialized Unity files. ## Workflow 1. Read `mcpforunity://editor/state` and stop if the editor is compiling, reloading, or not ready. 2. Read `mcpforunity://project/info`; record Unity version, render pipeline, installed UI/input packages, and project root. 3. Read installed packages with `manage_packages(action="list")`. Query package details before changing dependencies. 4. Inspect existing scenes, tags, layers, physics settings, and pipeline settings before mutation. 5. Propose the smallest configuration delta. Preserve the project's chosen pipeline and conventions unless the user asks for a migration. 6. Apply related independent changes with `batch_execute`; keep dependency-changing calls sequential and poll their job status. 7. Wait for imports and compilation, then read console errors and warnings. 8. Save affected scenes/assets and report exact packages and settings changed. ## Package Rules - Use `manage_packages`; never hand-edit `Packages/manifest.json` while the Editor is connected. - Prefer released package versions compatible with the detected Editor. Use `unity_docs` or package info instead of guessing versions. - Check dependents before removal. Use force only after explaining what will break. - Treat Git URLs and scoped registries as supply-chain changes; show the source before installing. - Install only what the requested workflow needs. Typical optional packages include Input System, Cinemachine, ProBuilder, UI Toolkit dependencies, Test Framework, Memory Profiler, and platform-specific packages. ## Project Configuration - Use `manage_editor` for tags and layers; read existing names first and avoid repurposing occupied slots. - Use `manage_build(action="scenes")` to audit or update build scenes. - Use `manage_graphics(action="ping")` and pipeline query actions before URP/HDRP changes. - Use `manage_physics` with `dimension="2d"` or `dimension="3d"`; do not mix settings implicitly. - Create reusable configuration as ScriptableObjects when it is project data, not scene state. - For multiple open Editors, list instances and call `set_active_instance` before changing anything. ## Verification Gate Do not call setup complete until the Editor is ready, the console has no new compile errors, installed packages match the plan, and at least one target scene opens successfully. For exact tool parameters, read the shared [tool reference](../unity-mcp-skill/references/tools-reference.md) only for the tools used.