Code Review

Check Unity best practices:

• No LINQ allocations in hot paths (Update, physics callbacks)
• Object pooling used for frequently instantiated objects
• NonAlloc physics APIs used where applicable
• No allocations in Update() (check for string concatenation, new in loops)
• Coroutines: StopCoroutine called where needed

Check architectural compliance:

• Correct dependency direction (engine ← gameplay, not reverse)
• No circular dependencies between assemblies
• UI does not own game state
• Events/delegates used for cross-system communication
• Interfaces expose system contracts

Check SOLID compliance:

• Single Responsibility (SRP): each class has one reason to change
• Open/Closed (OCP): extendable without modification (via interfaces/inheritance)
• Liskov Substitution (LSP): subtypes must be substitutable for their base types without altering correctness
• Interface Segregation (ISP): prefer small, focused interfaces over large monolithic ones
• Dependency Inversion (DIP): depends on abstractions, not concretions

Check KISS and DRY compliance:

• KISS: no over-engineered abstractions — simplest solution that meets requirements
• KISS: no unnecessary complexity — favor readability over cleverness
• DRY: no duplicated logic across 3+ locations — extract shared abstractions
• DRY: configuration data reused via ScriptableObjects, not copy-pasted

Output the review in this format: