skills.rest
dimsour
dimsourCOMMUNITY
Explore all skills by this author →
GitHub

boundaries

Analyze .NET project structure for Clean Architecture boundary violations.

2|Updated Apr 19, 2026
Search Tags:#clean architecture#dependency analysis#project validation#boundary analysis#namespace layering
One-click install
npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill boundaries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: boundaries
Source: https://github.com/dimsour/dotnet-ai-toolkit/tree/main/plugins/dotnet-copilot/skills/boundaries
Command: npx skills add https://github.com/dimsour/dotnet-ai-toolkit --skill boundaries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotnet-depends, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and reports on boundary issues within .NET project structures, helping to maintain adherence to Clean Architecture patterns and prevent circular dependencies and layering violations.

Core Features & Use Cases

  • Boundary Analysis: Detects circular references, namespace layering issues, and public API surface concerns.
  • Project Validation: Pre-refactor checks and refactoring suggestions for clean and maintainable code.
  • Use Case: Before a major refactor, use this Skill to uncover and fix project boundaries that violate Clean Architecture principles, such as incorrect layering or circular dependencies.

Quick Start

Run the boundaries skill with your project to validate the architecture of 'MyApp.csproj'.

Frequently Asked Questions about boundaries

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

FAQPage Schema
How do I detect circular dependencies and layering violations in a .NET project?▼

To analyze .NET project structure for Clean Architecture adherence, you run the analysis against your project file, such as 'MyApp.csproj'. It evaluates project metadata and namespace layering to produce detailed architectural reports and refactoring suggestions.

What is namespace layering analysis and when do I need it for a refactoring process?▼

Yes, dependency analysis works with .NET projects by examining project metadata and custom scripts to identify architectural boundary issues. It specifically targets .NET project structures to detect public API surface concerns and layering violations.

Do I need dotnet-depends to perform .NET project validation?▼

Yes, you need dotnet-depends to perform .NET project validation because it is a required dependency for this analysis. It enables the underlying dependency analysis required to detect circular references and validate your project's architecture.

What is the best way to ensure .NET project architecture integrity before a major refactor?▼

The best way to ensure .NET project architecture integrity is to run a pre-refactor boundary analysis to detect circular dependencies and incorrect layering. This process provides targeted refactoring suggestions to fix architectural issues and maintain Clean Architecture patterns.

Related Skills

Explore More Software Engineering Skills→
AarononthewebAaronontheweb
1.1k

dotnet-local-tools

Manage per-repo .NET CLI tools via dotnet-tools.json manifests.

Community
Intermediate
oliver-kriskaoliver-kriska
517

phx:boundaries

Validate Phoenix context boundaries and dependencies using mix xref.

Community
Intermediate
gautam-achieveaigautam-achieveai
2

clean-builds

Automates code quality tools and package version validation in .NET projects.

Community
Advanced
managedcodemanagedcode
466

dotnet-code-analysis

Configure .NET projects with Roslyn analyzers and .editorconfig rules.

Official
Advanced