skilld
All skills
openai avatar

/aspnet-core

@c207989 official
by openaiopenai/skills28k stars
1,891

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/aspnet-core

This session only. Nothing lands on disk.

referencesstack-selection.md

≈925 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Stack Selection

Primary docs:

Default Version Choice

  • Prefer the latest stable .NET and ASP.NET Core for new production work.
  • As of March 2026, that means net10.0 unless the repository or user request says otherwise.
  • Treat ASP.NET Core 11 as preview. Do not adopt preview APIs by default.
  • If the repository already targets net8.0, net9.0, or another framework, stay within that target unless the task is explicitly an upgrade.

Template Short Names

The current .NET 10 SDK templates include:

  • dotnet new blazor
  • dotnet new webapp
  • dotnet new mvc
  • dotnet new webapi
  • dotnet new webapiaot
  • dotnet new grpc
  • dotnet new web
  • dotnet new razorclasslib

Verify template names with dotnet new list if the environment differs.

Application Model Matrix

Model Prefer when Watch out for Typical starting point
Blazor Web App Build full-stack .NET UI with SSR plus optional interactivity Interactive server needs a live connection; WebAssembly increases payload size dotnet new blazor
Razor Pages Build page-focused CRUD, forms, dashboards, and line-of-business apps Authorization cannot be applied per page handler; use MVC if handler-level control matters dotnet new webapp
MVC Build large server-rendered apps with clear controller/view separation, filters, and action-based patterns More ceremony than Razor Pages for simple page flows dotnet new mvc
Minimal APIs Build focused HTTP APIs, internal services, lightweight backends, and small surface areas Route handlers can become hard to manage if business logic or metadata grows without structure dotnet new webapi or dotnet new web
Controller-based Web API Build APIs that benefit from [ApiController], content negotiation, filters, formatters, and mature controller conventions More ceremony than Minimal APIs for small endpoints dotnet new webapi
SignalR Add server push, live updates, chat, collaborative UI, or notifications Requires connection lifecycle management and scale-out planning Add to an existing ASP.NET Core app
gRPC Build service-to-service or streaming RPC over HTTP/2 Browser support is different from ordinary JSON APIs; use gRPC-Web only when needed dotnet new grpc

Fast Heuristics

  • Choose Blazor Web App when the UI itself should be a .NET component model.
  • Choose Razor Pages when the app is mostly page and form oriented.
  • Choose MVC when actions, views, filters, and controller conventions are the center of the design.
  • Choose Minimal APIs first for small to medium HTTP services.
  • Switch to controllers when the API needs richer attribute-driven behavior, custom formatters, or strong alignment with existing MVC/Web API conventions.
  • Keep the current app model in an existing codebase unless the mismatch is causing real complexity.

Mixed-Model Guidance

ASP.NET Core can mix models in one host. Common combinations:

  • Razor Pages or MVC for server-rendered UI plus Minimal APIs for AJAX or mobile endpoints
  • Blazor Web App plus Minimal APIs for external integration endpoints
  • MVC or Razor Pages plus SignalR for live updates
  • Web API plus gRPC for internal service-to-service calls

Mix models only when it simplifies the public surface. Do not add a second app model just because ASP.NET Core allows it.

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides a comprehensive set of guidelines and reference materials for ASP.NET Core development, emphasizing security best practices and official architectural patterns. It does not contain any malicious patterns or unauthorized operations.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    6/16 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at c207989. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 7 months ago

Topics

  • Testing
  • aspnet-core
  • dotnet
  • csharp
  • blazor
  • razor-pages
  • mvc
  • minimal-apis
  • ef-core
  • signalr
  • grpc
  • authentication

README badge

README badge for openai/skills/aspnet-core

What it does

Instructs Claude on ASP.NET Core application models (Blazor Web Apps, Razor Pages, MVC, Minimal APIs), host and pipeline setup, dependency injection, configuration, authentication, testing, and deployment using current Microsoft documentation. Use for building or refactoring .NET web applications and deciding between framework patterns.

Generated from the current SKILL.md.

Frequently asked

Does this skill cover Blazor, Razor Pages, MVC, and Minimal APIs?
Yes. The skill includes dedicated references for each application model (Blazor Web Apps, Razor Pages, MVC, and Minimal/controller-based APIs) and guides you to load only the one you need for your task.
What .NET versions does this skill target?
The skill defaults to .NET 10 / ASP.NET Core 10 for new production work as of March 2026, but adapts to older pinned versions and handles migrations between major versions via the versioning-and-upgrades reference.
Does this skill use third-party libraries or stick to built-in ASP.NET Core features?
The skill prefers built-in features (DI, options, logging, ProblemDetails, OpenAPI, health checks, rate limiting, Identity) before introducing third-party infrastructure.
Can this skill help with authentication, authorization, and data access?
Yes. Cross-cutting references cover security/identity, EF Core, DbContext, and state management, loaded on-demand based on your specific task.
Does this skill guide upgrades from older ASP.NET Core versions?
Yes. The versioning-and-upgrades reference specifically handles breaking changes, obsolete APIs, and migrations between major versions.

Generated from the current SKILL.md. These answers refresh after source changes.