Unity Developer Skill — Wildcard Forest

Automate Unity C# code quality checks by running the CLI compilation gate before commits to enforce zero compilation errors, passing tests, and proper scene wiring. This workflow applies assembly boundaries and data-driven patterns to verify your Unity project.

Enforcing assembly boundaries in Unity development requires defining strict architectural targets and data-driven patterns for your C# scripts. This skill provides detailed guidance on assembly conventions and gradual migration strategies to maintain structural integrity.

Yes, this Unity development workflow supports both MCP and CLI modes for project verification. It applies specific gate rules for each implementation mode to ensure your C# code meets strict quality and testing standards.

Verify Unity scene wiring and ensure zero compilation errors by executing the Unity Editor CLI tools provided. The automated testing framework checks scene wiring integrity and reports any compilation failures before changes are committed.

Yes, you need the Unity Editor and CLI tools installed to run automated testing workflows. The compilation and testing gates require the Unity Editor environment to validate C# scripts and enforce development standards.

The best way to migrate legacy Unity C# scripts to data-driven patterns is to follow a gradual migration strategy. This skill provides documentation on architectural targets and code conventions to systematically transition your existing project.