What problem does it solve? Unity components often expose fields in the Inspector in ways that confuse designers and teammates—public fields everywhere, no grouping, no constraints, and unclear defaults. This Skill provides guidance for designing clean, reviewable Inspector presentations so scripts are easier to author, configure, and validate. ## Core Features & Use Cases - Field Exposure Strategy: Recommends [SerializeField] private over unnecessary public fields and SerializeReference only when polymorphic data is genuinely needed. - Attribute Organization: Advises on [Header], [Tooltip], [Space], [Range], [Min], [TextArea], [RequireComponent], and [CreateAssetMenu] usage to clarify authoring intent. - Validation Guidance: Covers lightweight OnValidate editor-time validation and normalization, plus an Inspector quality checklist covering defaults, grouping, constraints, and debug-field separation. - Use Case: When writing a new MonoBehaviour with tunable gameplay values, use this Skill to decide which fields to expose, how to group and constrain them, and what validation to add so another team member understands the component from the Inspector alone. ## Quick Start Ask the AI to review your Unity component's serialized fields and recommend Inspector attributes, grouping, and validation for better authoring UX.
