Unity Script Design Review

Documentation only: no REST skills. Use before creating gameplay scripts, or after scripts are generated and need a design pass.

When to use

• Reviewing code quality
• Untangling tightly coupled scripts
• Planning a refactor for maintainability

Review checklist

• Responsibility: does the script have one clear job?
• Role: should it be a MonoBehaviour, ScriptableObject, or plain C# class?
• Coupling: are dependencies explicit instead of hidden globals or deep scene lookups?
• Communication: direct reference, interface call, or event?
• Performance: unnecessary Update, repeated Find, avoidable allocation, or reflection in hot paths?
• Lifecycle: are subscriptions, timers, and async work cleaned up clearly?
• Inspector UX: are serialized fields private, grouped, and explained?
• Testability: can the core logic move into a plain C# class?
• Naming: do class and field names explain intent without cryptic abbreviations?