dotnet

To route a .NET monorepo, the skill classifies the repository by analyzing project SDKs and target frameworks to detect the primary app model, then hands off to the narrowest specialized skill for precise code generation guidance.

Framework-specific skill handoff supports detecting common .NET app models including ASP.NET Core, Blazor, MAUI, and Entity Framework, ensuring the repository receives accurate, specialized guidance instead of generic advice.

App-model detection is needed for multi-framework .NET codebases when you require precise handoff for code generation, review, or quality checks, validating repo compatibility to ensure accurate framework-specific guidance across the detected stack.

Yes, the .NET skill router works with Blazor and MAUI project SDKs by performing target framework analysis to identify the primary app model and route the repository to the appropriate specialized skill.

You can avoid generic .NET guidance by using the router to classify your ASP.NET Core repository, which identifies the primary app model and routes it to the narrowest matching specialized skill for accurate, framework-specific code analysis.

The best way to validate repo compatibility is to apply project SDK detection and target framework analysis, which identifies the app model and ensures the codebase is routed to a compatible specialized skill for generation.