unity-project-scout

To analyze a Unity project, run a reconnaissance scan that surfaces the Unity version, render pipeline, installed packages, asmdef layout, and Assets folder structure to establish a technical baseline. This assessment documents existing patterns, naming conventions, and constraints to guide architecture decisions.

You can detect architectural signals in a Unity codebase by scanning for ScriptableObject usage, service or singleton patterns, event-driven flows, custom inspectors, and test frameworks. These signals reveal established conventions and risks without disrupting the current project.

Generate a baseline assessment by scanning an existing Unity project to identify config usage, asmdef layout, installed packages, and folder structure under Assets. The resulting report documents technical constraints, detected patterns, and architectural risks to inform future modifications.

Yes, you can assess Unity asmdef layout and Assets folder structure by running a project reconnaissance script that parses the project files directly. This approach extracts version, render pipeline, and dependency data without launching the Unity editor or disrupting the environment.

You need to document constraints in a Unity project baseline before making any architecture changes, ensuring that existing signals, risks, and technical limitations are visible. This practice avoids recommending a clean-slate architecture and grounds decisions in the current codebase reality.

The best way to identify installed packages and render pipeline is to run a project reconnaissance scan that extracts package manifest data and pipeline settings directly. This establishes a technical baseline detailing dependencies and rendering configuration without altering the project.