unity-project-scout

Scouting a Unity project involves reading the Unity version, render pipeline, Packages/manifest.json, and asmdef structure. This reconnaissance outputs a preserved baseline of conventions, constraints, and unknowns to prevent architectural misalignment.

Unity project reconnaissance is the process of inspecting an unknown codebase's dependencies, asmdef layout, and coding conventions. You need it to avoid breaking existing patterns and proposing architectural changes that conflict with the current setup.

Mapping asmdef structure and Assets organization involves inspecting how Unity systems are modularized and wired. This detects architectural signals like ScriptableObject configurations, event-driven flows, and service patterns to align future recommendations.

You can detect existing coding patterns by inspecting the Unity codebase for architecture signals like ScriptableObject configurations, service patterns, event-driven flows, custom inspectors, and tests. This ensures suggested architecture aligns with what already exists.

Analyzing Unity dependencies involves reviewing Packages/manifest.json, the render pipeline, and Unity version. This dependency review produces a technical baseline of preserved conventions, constraints, and open unknowns to safely guide architectural recommendations.

Scouting limitations include relying on visible evidence like asmdefs and Assets layout, which may miss runtime behaviors. The reconnaissance outputs remaining unknowns and constraints, indicating that some architectural signals cannot be fully verified without deeper inspection.