using-dotnet

Detect .NET intent from prompts and repository signals to route domain skills.

2|Updated Mar 17, 2026

Search Tags:#csharp #routing #dotnet #coding-standards #advisor #aspnet

Ready to run

npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill using-dotnet-sayedihashimi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: using-dotnet
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/plugins/dotnet-artisan/skills/using-dotnet
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill using-dotnet-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects .NET intent from prompts and repository signals and routes to the appropriate dotnet domain skills via [skill:dotnet-advisor], ensuring version-aware guidance from the start.

Core Features & Use Cases

Detects .NET intent from keywords and repo markers and routes to dotnet domain skills before planning.
Enforces routing discipline to load dotnet-advisor and baseline dotnet skills for consistent code guidance.
Supports multiple .NET project types and repository signals to maintain correct execution order.

Quick Start

Ask Copilot to route a .NET task to the advisor and load the appropriate domain skills.

Frequently Asked Questions about using-dotnet

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

FAQPage Schema

How do I route .NET prompts to the correct domain skills in Copilot?▼

Routing .NET prompts involves detecting C#, ASP.NET, EF Core, or Blazor keywords and repository cues like .sln and .csproj files, then loading the dotnet-advisor and baseline skills to apply version-aware coding standards.

What repository signals trigger .NET skill routing automatically?▼

Repository signals that trigger .NET routing include .sln, .csproj, global.json, and .cs files, which ensure proper engagement of the dotnet-advisor and domain skills before implementation.

Do I need a .sln file to use .NET coding standards advisor skills?▼

A .sln file is not strictly required; the advisor detects .NET intent from prompt keywords like C# and Blazor, or other repository markers such as .csproj, global.json, and .cs files.

Does ASP.NET and EF Core intent detection work without repository files?▼

Yes, ASP.NET and EF Core intent detection works without repository files by scanning prompt text for .NET keywords like C# and Blazor, routing tasks to the correct domain skills.

What's the best way to enforce version-aware coding standards in ASP.NET projects?▼

To enforce version-aware coding standards, route ASP.NET tasks through the dotnet-advisor, which loads baseline skills and applies version-specific guidance before implementation starts.

Why does my C# prompt not trigger the dotnet-advisor skill?▼

Your C# prompt may not trigger the advisor if it lacks clear .NET keywords or repository signals like .csproj and global.json, which are required to detect .NET intent and route to domain skills.