Agent skill · software engineering · openai
aspnet-core
Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.
Why this skill is useful
Provides domain-specific guidance on structuring ASP.NET Core applications, including references and best practices not commonly known.
What it needs
About 2k tokens when loaded. Last updated 2026-07-14. 24,594 stars on the source repository.
What this skill does
ASP.NET Core Overview Choose the right ASP.NET Core application model, compose the host and request pipeline correctly, and implement features in the framework style Microsoft documents today. Load the smallest set of references that fits the task. Do not load every reference by default. Workflow 1. Confirm the target framework, SDK, and current app model. 2. Open references/stack-selection.md first for new apps or major refactors. 3. Open references/program-and-pipeline.md next for Program.cs, DI, configuration, middleware, routing, logging, and static assets. 4. Open exactly one primary app-model reference: references/ui-blazor.md references/ui-razor-pages.md references/ui-mvc.md references/apis-minimal-and-controllers.md 5. Add cross-cutting references only as needed: references/data-state-and-services.md references/security-and-identity.md references/realtime-grpc-and-background-work.md references/testing-performance-and-operations.md 6. Open references/versioning-and-upgrades.md before introducing new platform APIs into an older solution or when migrating between major versions. 7. Use references/source-map.md when you need the Microsoft Learn section that corresponds to a task not already covered by the focused references. Default Operating Assumptions Prefer the latest stable ASP.NET Core and .NET unless the repository or user request pins an older target. As of March 2026, prefer .NET 10 / ASP.NET Core 10 for new production work. Treat ASP.NET Core 11 as preview unless the user explicitly asks for preview features. Prefer WebApplicationBuilder and WebApplication. Avoid older Startup and WebHost patterns unless the codebase already uses them or the task is migration. Prefer built-in DI, options/configuration, logging, ProblemDetails, OpenAPI, health checks, rate limiting, output caching, and Identity before adding third-party infrastructure. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills openai/aspnet-core