dotnet

Classifies .NET repositories by app model and routes tasks to specialized framework skills.

Updated May 2, 2026
One-click install
npx skills add https://github.com/hdeshev/pi-config --skill dotnet-hdeshev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet
Source: https://github.com/hdeshev/pi-config/tree/main/agent/skills/dotnet
Command: npx skills add https://github.com/hdeshev/pi-config --skill dotnet-hdeshev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? General .NET requests often lack a clear framework context, leading to generic advice that ignores the actual stack. This Skill inspects the repository's SDKs, target frameworks, workloads, and tooling, then hands the task off to the narrowest matching specialized .NET skill. ## Core Features & Use Cases - Stack Detection: Identifies project SDKs, target framework monikers, LangVersion, workloads, test frameworks, analyzers, and coverage tools from project files and configuration. - Skill Routing: Routes work to platform skills (aspnet-core, blazor, maui, wpf, orleans, semantic-kernel, and more) or cross-cutting skills (xunit, code-review, format, coverlet, architecture) based on detected indicators. - Use Case: A user asks to add a feature in a repo containing .razor files and xUnit tests. The Skill detects Blazor via project indicators, routes implementation to the blazor skill, and routes test work to the xunit skill. ## Quick Start Analyze this .NET repository and tell me which specialized skill should handle adding a new API endpoint with tests.

Frequently Asked Questions about dotnet

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

FAQPage Schema
How do I choose the right .NET skill for a task?▼

Detect the repo's app model first using project SDKs, target frameworks, and package indicators, then route to the narrowest matching skill. For example, Microsoft.NET.Sdk.Web indicates a web skill, while .razor files indicate blazor.

How to detect which .NET framework a project uses?▼

Check the Project Sdk attribute in csproj files, the TargetFramework moniker, global.json for SDK version, and packages like Microsoft.EntityFrameworkCore or Microsoft.Maui. These indicators map directly to app models such as web, desktop, or data.

When should a task stay at the generic dotnet skill?▼

Stay at the generic skill only when no narrower specialization matches the task. Be explicit about the missing specialization and avoid giving generic advice when a framework-specific skill exists.

How are multi-skill .NET tasks handled?▼

Prefer the skill closest to user-visible behavior first, such as blazor for a UI feature, then pull in quality or tooling skills like xunit or coverlet second. Runner-specific commands should come from one skill at a time.

What are the limitations of a router skill for .NET?▼

A router skill only classifies and hands off; it does not provide deep framework guidance itself. If the target specialized skill does not exist in the catalog, it can only offer generic .NET guidance and note the gap.