Verified:GitHub

dotnet-solution-navigation

Parse .sln/.slnx files and map project dependencies in .NET solutions.

10|Updated Jan 28, 2026

Search Tags:#codebase analysis #.net #entry points #solution navigation #project dependencies #configuration files

One-click install

npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-solution-navigation

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: dotnet-solution-navigation
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-solution-navigation
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-solution-navigation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps agents understand the structure of .NET solutions, making it easier to find entry points, understand project dependencies, and locate configuration files.

Core Features & Use Cases

Entry Point Discovery: Identifies various application starting 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 ProjectReference relationships to understand build order and impact analysis.
Configuration Location: Finds appsettings*.json, launchSettings.json, Directory.Build.props/targets, and other common config files.
Layout Recognition: Identifies common solution structures like src/tests, vertical slices, and modular monoliths.
Use Case: When presented with a new .NET codebase, an agent can use this Skill to quickly map out all projects, their dependencies, and identify the main application entry points.

Quick Start

Use the dotnet-solution-navigation skill to find all .sln 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 find the entry point in a .NET solution?▼

To find the .NET solution entry point, you can use a tool that identifies application starting points like Program.cs with Main, top-level statements, worker services, and test projects.

Can I parse .sln and .slnx files to map project dependencies?▼

Yes, parsing .sln and .slnx formats allows you to list projects, map ProjectReference relationships, and understand build order for dependency traversal.

How do I locate configuration files in a .NET codebase?▼

Locating .NET configuration files involves finding appsettings*.json, launchSettings.json, and Directory.Build.props/targets to understand the environment setup.

What is the best way to analyze a new .NET codebase structure?▼

Analyzing a new .NET codebase structure involves recognizing common layouts like src/tests, vertical slices, and modular monoliths to map out all projects and dependencies.

Does .NET solution navigation support worker services and test projects?▼

Yes, .NET solution navigation supports worker services and test projects by identifying them as valid application starting points during entry point discovery.