unity-perception

You can export a Unity scene hierarchy and component data by running a scene context command to generate a structured markdown report of references and components. This provides AI-ready spatial and hierarchy intelligence for coding guidance.

Yes, you can perform a safe-to-delete impact assessment by analyzing the read-only dependency graph and reference structure of the Unity scene. This identifies what depends on the target object before you make deletion edits.

The best way to analyze Unity scene health is to run a read-only inspection pass that detects deep hierarchy groups and hygiene hotspots. This diagnosis evaluates structural issues while ensuring no scene modifications occur.

Yes, this approach supports script dependency graph closure queries to identify involved packages and code dependencies. It validates scene conventions and traces script references within the project for accurate refactoring planning.

You generate a snapshot diff by exporting structured scene context before and after your planned Unity edits. This workflow validates scene conventions and captures dependency insights to ensure low-risk refactoring outcomes.

Yes, you can execute targeted spatial queries against the exported Unity scene context to identify objects near a specific location. This read-only inspection provides material and spatial data for debugging and analysis.