agency-unity-editor-tool-developer

Automate Unity Editor workflows using AssetPostprocessor import rules and pre-build validation to enforce naming conventions, platform compression, and resolution budgets, blocking builds when critical policies are violated.

Enforce texture import settings automatically in Unity by applying AssetPostprocessor rules that validate resolution budgets, auto-clamp UI asset compression, and enforce naming conventions at import time to reduce manual asset handling.

Yes, you can run CI-friendly headless validation in Unity by executing pre-build validators that check for policy violations like oversized textures or incorrect import settings, failing the build automatically if critical rules are breached.

The best way to build a Unity EditorWindow for asset auditing is to create a custom UI that surfaces project state, lists affected file paths for oversized textures, and provides actionable recommendations for fixing import settings without leaving the Editor.

You need asmdef separation for Unity Editor tools to enforce editor-only execution, ensuring that EditorWindow scripts, PropertyDrawer inspectors, and AssetPostprocessor logic do not compile into player builds and cause runtime errors.

Yes, Unity AssetPostprocessor supports idempotent import rules to prevent duplicate processing on reimport, alongside Undo and progress UX implementations to ensure safe, trackable editor tooling operations within the development environment.