unity-inspector

Organize Unity Inspector fields by applying attributes like [Header], [Space], and [Tooltip] to group related data and expose authoring intent. This reorganization helps developers understand component configuration quickly and reduces editing errors.

Constrain tuning values in the Unity Inspector by applying [Range] and [Min] attributes to serialized fields. This restricts editable values to safe limits, preventing designers from entering extreme numbers that break component behavior.

Prefer [SerializeField] private over public for Unity Inspector exposure to maintain encapsulation while allowing editor serialization. This approach keeps your component architecture safer from external scripts while still enabling designer authoring.

OnValidate works in Unity by automatically executing whenever an Inspector field changes, allowing lightweight validation and data normalization. You can use it to enforce dependencies, clamp values, or reset invalid configurations during editor time.

You need [RequireComponent] when your MonoBehaviour depends on sibling components to function correctly. Adding this attribute prevents broken Inspector setups by automatically ensuring mandatory dependencies are present and cannot be accidentally removed.