using-dotnet

Route .NET and C# tasks to dotnet-advisor before planning or implementation.

46|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill using-dotnet-sunyonghuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-dotnet
Source: https://github.com/sunyonghuan/Netor.Madorin/tree/main/.github/skills/using-dotnet
Command: npx skills add https://github.com/sunyonghuan/Netor.Madorin --skill using-dotnet-sunyonghuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect or stale guidance on .NET and C# tasks by forcing an early routing step before any planning, clarification, or implementation. It helps the assistant recognize when a request belongs in the .NET ecosystem and ensures the right version-aware standards are loaded first.

Core Features & Use Cases

  • Intent Detection: Identifies .NET work from prompt keywords and repository signals such as solution files, project files, global.json, and C# sources.
  • Routing Discipline: Requires the assistant to invoke dotnet-advisor before any coding, planning, or command execution.
  • Common Use Cases: Use it for ASP.NET Core apps, Blazor, MAUI, WPF, WinUI, EF Core, gRPC, xUnit, NuGet, and MSBuild tasks.
  • Workflow Control: Keeps .NET requests on the correct path so downstream domain skills and baseline guidance load in the proper order.

Quick Start

Ask the assistant to apply the using-dotnet skill first, then route the task through dotnet-advisor before any planning or implementation.

Frequently Asked Questions about using-dotnet

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

FAQPage Schema
How do I ensure correct version-aware guidance when working with ASP.NET Core and EF Core?

Routing .NET work before planning identifies C# ecosystem intent from solution files and prompt keywords, then mandates a handoff to load baseline guidance. This prevents incorrect or stale advice by ensuring the right version-aware standards load first.

Can I use this routing approach for Blazor, MAUI, and WPF project tasks?

Yes, you can use this routing approach for Blazor, MAUI, and WPF tasks. It applies intent detection to any prompt or repository involving C# sources, ensuring the assistant recognizes the .NET ecosystem and routes to the correct domain skills.

What is .NET intent detection and when do I need it for MSBuild or NuGet tasks?

.NET intent detection is the process of identifying .NET work from prompt keywords and repository signals like global.json and project files. You need it for MSBuild or NuGet tasks to force an early routing step before implementation, preventing incorrect guidance.

How do I route C# coding requests before command execution or clarification?

Route C# coding requests by applying a routing discipline that requires invoking an advisor before any command execution, clarification, or planning. This keeps .NET requests on the correct path so downstream domain skills load in the proper order.

Does this routing skill support SignalR and gRPC frameworks?

Yes, this routing skill supports SignalR and gRPC frameworks. It explicitly applies to prompts and repositories involving these technologies, ensuring baseline .NET guidance is loaded before any coding or planning begins.