unity-inspector

Advise on Unity Inspector field organization, attributes, and authoring UX.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-inspector-ethanjpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-inspector
Source: https://github.com/ethanJPope/Our-Main-Hackathon-Game/tree/main/.agents/skills/unity-skills/skills/inspector
Command: npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-inspector-ethanjpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity scripts often expose fields in the Inspector in ways that confuse designers and teammates, leading to misconfiguration and hard-to-review components. This Skill provides guidance for organizing serialized fields, applying the right attributes, and improving authoring UX in the Unity Inspector. ## Core Features & Use Cases - Field Exposure Strategy: Recommends [SerializeField] private over unnecessary public fields and clarifies when SerializeReference is appropriate. - Attribute Guidance: Advises on [Header], [Tooltip], [Space], [Range], [Min], [TextArea], [RequireComponent], and [CreateAssetMenu] usage. - Inspector Quality Checklist: Reviews defaults, grouping, constraints, and separation of debug-only fields from authoring fields. - Use Case: When writing a new MonoBehaviour with many tunable values, use this Skill to decide which fields to expose, how to group them, and which validation attributes to apply so another developer can understand the component from the Inspector alone. ## Quick Start Review my Unity component's serialized fields and recommend Inspector attributes and organization for better authoring UX.

Frequently Asked Questions about unity-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize serialized fields in the Unity Inspector?

Group fields by responsibility using [Header] and [Space] attributes, and prefer [SerializeField] private over public fields. Add [Tooltip] to clarify intent and keep debug-only fields separated from authoring fields.

When should I use SerializeField vs public fields in Unity?

Prefer [SerializeField] private fields to expose data in the Inspector without widening your API surface. Use public fields only when other scripts genuinely need direct access to the value.

What Unity attributes improve Inspector readability?

Use [Header], [Tooltip], [Space], [Range], [Min], and [TextArea] when they clarify authoring intent. Avoid over-decorating fields when clear naming alone communicates the purpose.

When should I use OnValidate in Unity scripts?

Use OnValidate only for lightweight editor-time validation and normalization of serialized values. It is not suitable for heavy logic or runtime behavior, and it does not run in builds.

When is SerializeReference appropriate in Unity?

Use SerializeReference only when you genuinely need polymorphic serialized data, such as storing different subclasses in one field. For simple data, plain serializable classes or structs are simpler and safer.