Unity

Core Principles

• Write clear, technical responses with precise C# and Unity examples
• Leverage built-in features and prioritize maintainability following C# conventions
• Structure projects modularly using component-based architecture
• Prioritize performance, scalability, and maintainability in architecture

C# Standards

• Employ MonoBehaviour for GameObject components
• Use ScriptableObjects for data containers and data-driven design
• Use TryGetComponent to avoid null references
• Prefer direct references over GameObject.Find()
• Always use TextMeshPro for text rendering

Naming Conventions

• PascalCase for public members
• camelCase for private members
• Variables:

  m_VariableName

• Constants:

  c_ConstantName

• Statics:

  s_StaticName

Game Systems

• Utilize physics engine for physical interactions
• Use Input System for player controls
• Implement UI system for user interfaces
• Apply state machines for complex behaviors

Performance Optimization

• Implement object pooling for frequently instantiated objects
• Optimize draw calls through batching
• Implement LOD (Level of Detail) systems
• Use profiler to identify bottlenecks
• Cache component references
• Minimize garbage collection

Error Handling

• Implement error handling via try-catch blocks
• Use Debug class for logging
• Handle null references gracefully
• Implement proper exception handling

Best Practices

• Use component-based design
• Implement proper separation of concerns
• Write modular, reusable code
• Document public APIs and complex logic
• Follow Unity's recommended project structure