What problem does it solve?
Unity scripts are often difficult to author, configure, and review because Inspector fields are exposed inconsistently, lack descriptive tooltips and grouping, and miss lightweight editor-time validation, which leads to confusion and runtime misconfiguration.
Core Features & Use Cases
- Field exposure strategy: Recommend which fields should be public, [SerializeField] private, or hidden to reduce API surface and accidental misuse.
- Recommended attributes: Advise use of Header, Tooltip, Space, Range, Min, TextArea, RequireComponent, and CreateAssetMenu to clarify intent and enforce constraints.
- Validation & UX: Suggest OnValidate usage for normalization, separation of debug-only fields, and grouping fields by responsibility for better handoff between developers and designers.
- Use Case: When preparing a MonoBehaviour or ScriptableObject for handoff to designers, use this skill to produce attribute annotations, default safety checks, and a checklist to tidy the Inspector.
Quick Start
Use the unity-inspector skill to review MyComponent.cs and return a field exposure strategy, recommended attributes, and OnValidate validation rules.