What problem does it solve? Unity components often expose fields in the Inspector that are confusing, unvalidated, or poorly organized, making them hard for designers and teammates to configure correctly. This Skill provides concrete guidance on structuring serialized fields so components are self-explanatory in the editor. ## Core Features & Use Cases - Field Exposure Strategy: Recommends [SerializeField] private over public fields and when to use SerializeReference for polymorphic data. - Attribute Organization: Advises on Header, Tooltip, Space, Range, Min, and TextArea attributes plus RequireComponent and CreateAssetMenu usage. - Validation Guidance: Covers lightweight editor-time validation with OnValidate and an Inspector quality checklist. - Use Case: When writing a new MonoBehaviour with many tuning values, ask for an Inspector design review to get grouped fields, constrained ranges, and clear tooltips before sharing it with your team. ## Quick Start Ask the assistant to review your Unity component's serialized fields and suggest an Inspector layout with appropriate attributes and validation.