unity-inspector

Recommend Unity C# Inspector field exposure, attributes, and validation rules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mandexonla/Top-Down-Template --skill unity-inspector-mandexonla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-inspector
Source: https://github.com/mandexonla/Top-Down-Template/tree/main/.codex/skills/unity-skills/skills/inspector
Command: npx skills add https://github.com/mandexonla/Top-Down-Template --skill unity-inspector-mandexonla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity Inspector fields are often noisy, misconfigured, or expose implementation details that confuse designers and maintainers; this Skill helps authors choose safe defaults, clear labels, and appropriate attributes so scripts are easy to configure and review without running code.

Core Features & Use Cases

  • Field exposure strategy: guidance on when to use SerializeField private vs public, and when to hide or show fields.
  • Attribute recommendations: suggest Tooltip, Header, Range, Min, Space, TextArea, CreateAssetMenu, RequireComponent, and SerializeReference usage where appropriate.
  • Validation and UX: OnValidate rules, safe defaults, grouping fields by responsibility, and separating debug-only fields to improve authoring and designer workflows.
  • Use Case: Prepare a character controller script for designers by cleaning public surfaces, adding tooltips and ranges, and adding validation notices so tuning can be done directly in the Inspector.

Quick Start

Audit my Unity script and recommend a field exposure plan, attribute annotations, grouping, and basic OnValidate checks to improve Inspector clarity.

Frequently Asked Questions about unity-inspector

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

FAQPage Schema
How do I improve Unity Inspector clarity for MonoBehaviour scripts?

To improve Unity Inspector clarity, apply field exposure strategies using SerializeField for private fields, add Tooltip and Header attributes for grouping, and implement OnValidate rules to catch misconfigurations before runtime.

When should I use SerializeField instead of public fields in Unity?

Use SerializeField for private fields when you need Inspector visibility without exposing implementation details. This keeps the public API clean for designers while allowing serialized data editing, preventing unintended script dependencies.

What Unity attributes help organize Inspector fields for designers?

Tooltip, Header, Range, Min, Space, and TextArea attributes organize Inspector fields by adding labels, visual grouping, input constraints, and spacing, making scripts easier for designers to configure without code access.

How do I add validation checks to Unity Inspector fields?

Implement OnValidate in MonoBehaviour or ScriptableObject scripts to add validation checks. This method runs when Inspector values change, letting you enforce Range constraints, safe defaults, and catch configuration errors during editing.

Does RequireComponent work with ScriptableObject scripts in Unity?

RequireComponent is designed for MonoBehaviour scripts to enforce component dependencies on GameObjects. ScriptableObject scripts do not attach to GameObjects, so RequireComponent does not apply; use validation rules instead for asset references.

What is the best way to prepare Unity scripts for designer handoff?

Prepare Unity scripts for designer handoff by auditing field exposure, adding Tooltip and Range attributes, grouping fields with Header, separating debug-only fields, and adding OnValidate checks so tuning can be done directly in the Inspector.