unity-standards

To enforce Unity C# coding standards, load a centralized reference hub covering naming, formatting, lifecycle, dependency injection, and null-safety guidelines. This ensures consistent practices during writing, reviewing, and refactoring C# scripts.

Best practices for Unity C# lifecycle and serialization involve adhering to a canonical catalog of code standards. This provides specific guidelines for lifecycle methods, DI, serialization, and null-safety to reduce bugs during architecture planning.

Yes, you can automatically apply Unity C# development standards when delegating tasks by using a shared reference hub. It loads conventions consistently, ensuring all writing, debugging, and refactoring tasks align with project rules.

To review Unity C# code changes for architecture and null-safety compliance, apply a shared reference catalog during code review tasks. This enforces project conventions and identifies deviations from established coding standards.

Yes, using a Unity C# standards reference helps with refactoring existing codebases by providing canonical guidelines for naming, formatting, and dependency injection. This ensures refactored code aligns with project conventions and reduces onboarding time.