editor-data-tools

What problem does it solve?

Unity editor tooling often makes it hard to reliably inspect, validate, and debug authored data and DOTS/baker outputs without leaking cost into runtime builds.

Core Features & Use Cases

• Editor-only, isolation-first tooling: keep diagnostics and authoring helpers strictly in Editor/ folders or *.Editor.asmdef, and gate everything behind UNITY_EDITOR or editor menus.
• Actionable validators for assets and build gates: produce issue lists with severity, target, field paths, expected vs actual values, and fix suggestions, wired into import/build pipelines and batch menu checks.
• Inspectable ECS/DOTS bake results: design custom inspector/editor window flows to preview baker output and runtime ECS state for debugging without noisy Debug.Log spam.

Quick Start

Ask the AI to design an editor window and pure validator that checks a specific authoring component’s fields and reports null/mismatched values with a precise asset path and field path.