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.