dev-codebase-exploration

Start with a breadth-first scan of the Assets/ directory, then read README and .asmdef files to map module dependencies. Next find entry points like Bootstrapper.cs or GameManager.cs, review interfaces and data models, and only then read concrete implementations relevant to your question.

Exclude Packages/, Library/, and Plugins/ directories from all searches and reads unless investigating a related compile error. Focus analysis on Assets/ and use assembly definition files to understand module boundaries before opening any C# files.

Reading entire .prefab, .unity, or .asset files is discouraged because they are massive YAML documents. Instead use grep searches for specific component names, variables, or m_FileID references to extract only the information you need.

Read files inside ProjectSettings/ only when the task directly relates to rendering, physics, input, or build pipeline issues. For general architecture exploration, these files are out of scope and consume unnecessary context.

Breadth-first exploration deliberately skips areas like UI prefabs, networking packages, and third-party integrations to conserve tokens. The output includes a blind spots declaration so you can request targeted deep dives into skipped areas when needed.