dotnet:boundaries

Analyze .NET project boundaries and detect circular references.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-boundaries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet:boundaries
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet/skills/boundaries
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill dotnet-boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps analyze and validate project/namespace boundaries, detecting circular references and layering violations in .NET solutions, which is crucial before major refactors or to maintain Clean Architecture.

Core Features & Use Cases

  • Boundary Analysis: Inspects project and namespace boundaries.
  • Circular Ref Detection: Identifies circular references in dependencies.
  • Layering Validation: Checks for correct layering according to Clean Architecture principles.
  • Use Case: Before a major refactor, use this Skill to ensure your project's architecture adheres to best practices and identify any potential issues.

Quick Start

Analyze the boundaries of your project by running the command /dotnet:boundaries <optional: project name or path>.

Frequently Asked Questions about dotnet:boundaries

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

FAQPage Schema
How do I detect circular references in a .NET project before refactoring?

You can detect circular references in a .NET project by analyzing .csproj files and building dependency graphs to identify circular project dependencies and namespace boundary violations before refactoring.

What is the best way to validate layering according to Clean Architecture in .NET?

Validating Clean Architecture layering in .NET involves parsing .csproj files to build a dependency graph and checking namespace usage against expected layer boundaries to detect layering violations.

Can I analyze namespace boundaries across a .NET solution without external dependencies?

Yes, you can analyze namespace boundaries across a .NET solution directly because this boundary analysis operates by parsing .csproj files and building dependency graphs without requiring any external dependencies.

Why does my .NET solution have circular project references and how do I find them?

Circular project references occur when dependencies form a cycle. You find them by parsing .csproj files, building a dependency graph of your .NET solution, and detecting the cycles within that graph structure.

When do I need to run a circular reference and layering violation analysis on my codebase?

You need to run circular reference and layering violation analysis before major refactors or when maintaining Clean Architecture, ensuring your .NET solution adheres to proper project and namespace boundaries.

Does boundary analysis work with individual .NET projects or only full solutions?

Boundary analysis works with both individual .NET projects and full solutions, as you can provide an optional project name or path to validate specific boundaries or analyze the entire dependency graph.