ASP.NET Core
Builds, reviews and upgrades ASP.NET Core applications using current official guidance, from Blazor and Razor Pages to Minimal APIs, SignalR and authentication.
When to use it
- You are working on a Blazor, Razor Pages, MVC or Web API project.
- Middleware, dependency injection or configuration needs to follow current guidance.
- You are planning an ASP.NET Core upgrade.
A practical example
You ask
“Add a Minimal API endpoint for orders with validation and proper authorization.”
Your agent does
It follows the project’s existing conventions, adds the endpoint with validation and policy-based authorization, and notes how to test it.
What gets installed
The whole folder is copied, so scripts, references and any license notices stay together.
- agents/openai.yaml222 bytes
- assets/dotnet-logo.png2,270 bytes
- LICENSE.txt11,357 bytes
- references/_sections.md2,412 bytes
- references/apis-minimal-and-controllers.md3,040 bytes
- references/data-state-and-services.md2,422 bytes
- references/program-and-pipeline.md4,182 bytes
- references/realtime-grpc-and-background-work.md1,896 bytes
- references/security-and-identity.md2,941 bytes
- references/source-map.md2,040 bytes
- references/stack-selection.md3,700 bytes
- references/testing-performance-and-operations.md2,698 bytes
- references/ui-blazor.md2,478 bytes
- references/ui-mvc.md1,954 bytes
- references/ui-razor-pages.md1,937 bytes
- references/versioning-and-upgrades.md2,085 bytes
- SKILL.md5,539 bytes
Credit and license
Adapted from Microsoft’s ASP.NET Core skill. It’s shared under the Apache License 2.0, and the license file is installed with it however you choose to install.