What problem does it solve? Teams analyzing brownfield .NET systems often lack a current, trustworthy map of how the codebase is structured, so every change-impact question starts from guesswork. This Skill produces a baseline, reusable source-structure overview that later change-analysis work can reference by XID instead of re-reading the entire repository. ## Core Features & Use Cases - Whole-System Structure Mapping: Documents runtime units, major subsystems, startup/composition flow, request/event/job flows, state and persistence boundaries, and extension or plugin mechanisms for a confirmed source scope. - External Dependency Possibility Map: Records configuration keys, environment variables, build rules, queues, topics, schemas, and other external levers that can change runtime structure, with verification status for each. - Brownfield API Naming Extractor: Extracts local naming vocabularies (action verbs, business objects, lifecycle states, role suffixes, casing rules) and naming clusters that must stay aligned, so later design work can construct consistent names. - Use Case: Before asking how a specific modification affects a legacy .NET service, run this Skill on the service's solution to produce a registered source-structure finding that dotnet_change_analysis can select as target context. ## Quick Start Run the source_structure_overview skill against your target .NET repository or solution path with an explicit source scope boundary to produce a Markdown structure overview.
