EF6 to EF Core migration policy for .NET Framework to modern .NET upgrades. Use when: assessing EF6 usage, planning package compatibility, multitargeting projects with Entity Framework 6. EF Core is NOT supported on .NET Framework — EF6 packages must be retained during framework-to-modern-dotnet migration and only migrated to EF Core as a separate post-migration effort.
Launch a .NET Framework ASP.NET project using IIS Express from the command line, replicating how Visual Studio would run it. Use when the user wants to start, run, or test the web app locally during migration. Do NOT use for .NET Core or modern .NET apps — use dotnet run instead.
Addressing ASP.NET Identity dependency while upgrading from ASP.NET (.NET Framework) to ASP.NET Core.
System.Web adapters migration policy for ASP.NET Framework to ASP.NET Core. Use when: migrating System.Web.HttpContext, HttpRequest, HttpResponse, IHttpModule, IHttpHandler, HttpApplication, Global.asax, or other System.Web types to ASP.NET Core. Adapters are the DEFAULT approach during migration to minimize code changes. Covers adapter packages, property translations, incremental IHttpModule/IHttpHandler support, and behavioral differences (lifetime, threading, buffering). Native ASP.NET Core rewrite is a post-migration optimization.
Windows Service migration policy for .NET Framework ServiceBase to modern .NET BackgroundService. Use when: migrating System.ServiceProcess.ServiceBase, ServiceInstaller, ServiceProcessInstaller, or TopShelf-hosted services. The Generic Host + BackgroundService + Microsoft.Extensions.Hosting.WindowsServices pattern is the default approach. Both hosting packages target netstandard2.0 and .NET Framework 4.6.2+, enabling multitarget-first migration. Native rewrite from ServiceBase to BackgroundService can happen while still on net472.
Recommends the right GitHub Copilot customization type (instructions, prompt files, skills, agents, sub-agents, hooks) for a given intent. Use when the user asks which customization to use, whether something should be a skill or agent, or how to structure Copilot repo customizations.
Create and review skill files in .github/skills/. Use this skill when asked to create a new skill, review an existing skill, or improve skill quality. Applies best practices from agent-skills-best-practices.md to ensure skills are concise, discoverable, and effective.