unity-inspector

Advises on Unity Inspector field organization, attributes, and validation for component authoring.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/Dylan8865/FinalYearProject --skill unity-inspector-dylan8865
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-inspector
Source: https://github.com/Dylan8865/FinalYearProject/tree/main/GameDev/Tester/.agents/skills/unity-skills/skills/inspector
Command: npx skills add https://github.com/Dylan8865/FinalYearProject --skill unity-inspector-dylan8865

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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] to create sections, [Space] for separation, and [Tooltip] to explain each field's purpose. Keep debug-only fields separate from authoring fields so the Inspector stays readable.

Should I use public fields or SerializeField in Unity?▼

Prefer [SerializeField] private over public fields. This exposes the field in the Inspector for authoring while keeping it encapsulated from other scripts, reducing accidental external modification.

When should I use OnValidate in Unity scripts?▼

Use OnValidate only for lightweight editor-time validation and normalization, such as clamping values or auto-assigning references. Avoid heavy logic there since it runs frequently in the editor.

What Unity attributes improve Inspector usability?▼

Use [Header], [Tooltip], [Space], [Range], [Min], and [TextArea] when they clarify authoring intent. Add [RequireComponent] for mandatory sibling dependencies and [CreateAssetMenu] for designer-created data assets.

When should I use SerializeReference in Unity?▼

Use SerializeReference only when you genuinely need polymorphic serialized data, such as a list of mixed subtype instances. For simple cases, standard serialized fields or ScriptableObjects are simpler and safer.