dotnet-solution-navigation

Parse .NET solution files and traverse project dependencies to locate entry points.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-solution-navigation-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-solution-navigation
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-solution-navigation
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-solution-navigation-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers and AI agents quickly understand the structure and key components of a .NET solution, reducing the time spent on manual exploration.

Core Features & Use Cases

  • Entry Point Discovery: Identifies various application entry points (e.g., Program.cs with Main, top-level statements, worker services, test projects).
  • Solution File Parsing: Understands .sln and .slnx formats to list projects and their relationships.
  • Dependency Traversal: Maps project dependencies using ProjectReference to understand code relationships and impact analysis.
  • Configuration Location: Pinpoints appsettings*.json, launchSettings.json, Directory.Build.props/targets, and other configuration files.
  • Layout Recognition: Identifies common solution patterns like src/tests, Vertical Slice, and Modular Monolith.
  • Use Case: When presented with a new .NET codebase, use this Skill to identify the main web API project, its core domain models, and any configuration files that might affect its behavior.

Quick Start

Find all solution files in the current directory.

Frequently Asked Questions about dotnet-solution-navigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate a large .NET solution and understand its project structure?

To navigate a .NET solution, this Skill parses `.sln` and `.slnx` files to discover entry points, map project dependencies, and locate configuration files. It provides heuristics for understanding unfamiliar codebases and identifying common layouts like Vertical Slice or Modular Monolith.

How do I find entry points and configuration files in an unfamiliar .NET codebase?

Finding entry points and configuration files in a .NET codebase is done by identifying `Program.cs`, top-level statements, and worker services, while pinpointing `appsettings*.json`, `launchSettings.json`, and `Directory.Build.props` to understand application behavior.

What is the best way to map project dependencies and references in a .NET solution?

The best way to map project dependencies in a .NET solution is by traversing `ProjectReference` items. This Skill maps code relationships to support impact analysis and helps you understand how different projects within the solution interact.

Do I need the .NET SDK installed to explore solution files and project layouts?

Yes, you need the .NET 8.0+ SDK and the `dotnet` CLI installed to explore solution files. This Skill relies on the SDK environment to orient within the solution, discover entry points, and recognize common solution layouts.

Can I identify common .NET solution layouts like src/tests or Modular Monolith?

Yes, you can identify common .NET solution layouts. This Skill provides heuristics to recognize patterns such as `src/tests`, Vertical Slice, and Modular Monolith, helping you quickly understand the structural organization of the codebase.

Why does my AI agent struggle to traverse project dependencies in a .NET codebase?

Your AI agent may struggle to traverse project dependencies because it lacks heuristics for parsing `.sln` formats and mapping `ProjectReference` items. This Skill enables agents to orient within .NET solutions by discovering entry points and understanding code relationships.