uw-unity-project-setup

Automating Unity project bootstrap requires reading ProjectConfig.yaml to drive folder creation, package installation, and Git/MCP setup. This approach eliminates manual initialization errors by scaffolding the entire workspace structure end-to-end from that single configuration source.

Scaffolding a standard Unity folder structure is best handled by automated initialization from ProjectConfig.yaml. This process generates required directories like Assets/_Project/, Core, Features, Art, Scenes, and Tests based on your specified folder strategy, ensuring consistent workspace organization.

Yes, automated Unity project setup coordinates with Git and Unity MCP. It handles Git initialization and the initial commit, performs MCP status checks, and applies editor configuration guided by ProjectConfig.yaml to ensure the environment is fully connected.

Yes, you can generate documentation scaffolding during initialization. The setup process clones template documents including Game Design Documents, Technical Design Documents, and Game Feature Documents, while preparing prompts and logging if enabled in your configuration.

You do not strictly need Unity MCP as the sole method, because package installation supports manual scripts with optional fallback workflows. However, Unity MCP is the primary coordination tool used for package installation and status checks during the automated bootstrap.

Automated Unity project initialization is designed for new projects and first-time bootstraps. You should not use this approach for existing projects that already have established folder structures, Git repositories, or manually configured package dependencies.