unity-inspector

1> **Before calling any skill in this module:** if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via `GET /skills/recommend?includeSchema=true`) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.
2 
3## Triggers
4- Designing component Inspector display
5- Organizing serialized fields
6- Adding tooltips/headers
7- 设计组件在 Inspector 的呈现、组织序列化字段、添加提示/分组
8 
9# Unity Inspector Design
10 
11Use this skill when scripts need to be easier to author, configure, and review in the Inspector.
12 
13## Guardrails
14 
15> **Mode**: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).
16 
17- Prefer `[SerializeField] private` over unnecessary public fields.
18- Do not over-decorate with attributes when simple naming suffices.
19 
20## Default Rules
21 
22- Use `[Header]`, `[Tooltip]`, `[Space]`, `[Range]`, `[Min]`, `[TextArea]` when they clarify authoring intent.
23- Use `[RequireComponent]` for mandatory sibling dependencies.
24- Use `[CreateAssetMenu]` for config/data assets that designers should create directly.
25- Use `OnValidate` only for lightweight editor-time validation and normalization.
26- Use `SerializeReference` only when polymorphic serialized data is genuinely needed.
27 
28## Inspector Quality Checklist
29 
30- Are defaults safe?
31- Are required references obvious?
32- Are fields grouped by responsibility?
33- Are tuning values constrained?
34…