1---2name: dotnet-43description: "Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer. USE FOR: general .NET requests without a narrower framework; C# implementation, debugging, review, or refactoring; routing to framework and tooling skills. DO NOT USE FOR: unrelated stacks; tasks already covered by a narrower .NET skill. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."4compatibility: "Requires a .NET repository, solution, or project tree."5metadata:6 source: https://skillmd.com/skills/managedcode/dotnet-47---89# .NET Router Skill1011## Trigger On1213- the user asks for general `.NET` help without naming a narrower framework or tool14- implementing, debugging, reviewing, or refactoring C# or `.NET` code in a repo with multiple app models or frameworks15- deciding which `.NET` skill should own a task before editing code16- tasks that combine platform work with testing, quality, architecture, setup, or migration decisions1718## Workflow19201. Detect the real stack first:21 - target frameworks and SDK version22 - `LangVersion`23 - project SDKs and workload hints24 - hosting model and app entry points25 - test framework and runner26 - analyzers, formatters, coverage, and CI quality gates272. Route to the narrowest platform skill as soon as the stack is known:28 - Web: `aspnet-core`, `minimal-apis`, `web-api`, `blazor`, `signalr`, `grpc`29 - Cloud and hosting: `aspire`, `azure-functions`, `worker-services`30 - Desktop and client: `maui`, `wpf`, `winforms`, `winui`31 - Data and distributed: `entity-framework-core`, `entity-framework6`, `orleans`32 - AI and agentic: `semantic-kernel`, `microsoft-extensions-ai`, `microsoft-agent-framework`, `mlnet`, `mixed-reality`33 - Legacy: `legacy-aspnet`, `wcf`, `workflow-foundation`343. Route cross-cutting work to the companion skill instead of keeping it inside generic `.NET` advice:35 - project bootstrap or repo shape: `project-setup`, `architecture`36 - frontend asset analysis in mixed `.NET` plus Node repos: `eslint`, `stylelint`, `htmlhint`, `webhint`, `biome`, `sonarjs`, `metalint`, `chous`37 - code review: `code-review`38 - language features: `modern-csharp`39 - testing: `tunit`, `xunit`, `mstest`40 - format, analyzers, coverage, and CI: `format`, `code-analysis`, `quality-ci`, `coverlet`, `reportgenerator`41 - maintainability and architecture rules: `complexity`, `netarchtest`, `archunitnet`424. If more than one specialized skill applies, prefer the one closest to the user-visible behavior first, then pull in the quality or tooling skill second.435. Do not stop at this skill once a narrower match exists. This skill should classify and hand off, not become a generic dumping ground.446. After code changes, validate with the repository's actual build, test, and quality workflow instead of generic `.NET` commands.4546## Routing Heuristics4748- If the repo contains `Microsoft.NET.Sdk.Web`, start from a web skill, not generic `.NET`.49- If the repo contains Blazor, Razor Components, or `.razor` pages, prefer `blazor`.50- If the repo contains `package.json`, frontend lint configs, or browser-facing asset pipelines inside the `.NET` solution, prefer the dedicated frontend analysis skills instead of generic `.NET`.51- If the repo contains Orleans grains or silo hosting, prefer `orleans`.52- If the repo is mostly analyzers, CI, or coverage work, prefer the quality skill directly.53- If the user asks about “which skill should I use?”, answer with the narrowest matching skill and explain why in one short sentence.54- If no narrower skill matches, keep the work here and stay explicit about the missing specialization.5556## Deliver5758- the correct specialized skill choice for the task59- repo-compatible code or documentation changes that stay aligned with the detected stack60- validation evidence that matches the real project runner and quality toolchain6162## Validate6364- the chosen downstream skill actually exists in the catalog65- platform assumptions match project SDKs, packages, and workloads66- generic guidance has been replaced by framework-specific guidance whenever possible67- runner-specific commands are not mixed incorrectly68- language or runtime features are only used when the repo supports them6970## Documentation7172### References7374- [references/routing.md](references/routing.md) - Decision tree for routing tasks to specialized .NET skills, including app model classification and cross-cutting concern handling.75- [references/detection.md](references/detection.md) - Project detection patterns for identifying SDK types, target frameworks, workloads, language versions, and app models.