Index of every page on this site: llms.txt
All skills
openai avatar

/aspnet-core

@49f948f official
by openaiopenai/skills29k stars
2,023
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈97 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈8.5k more on demand in 14 files.

Description uses 4.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈390 characters, or 4.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:
  5. Add cross-cutting references only as needed:
  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.
  • Keep feature slices cohesive so the page, component, endpoint, controller, validation, service, data access, and tests are easy to trace.
  • Respect the existing app model. Do not rewrite Razor Pages to MVC or controllers to Minimal APIs without a clear reason.

Reference Guide

Execution Notes

  • When generating new code, start from the correct dotnet new template and keep the generated structure recognizable.
  • When editing an existing solution, follow the solution's conventions first and use these references to avoid framework misuse or outdated patterns.
  • When a task mentions "latest", verify the feature on Microsoft Learn or the ASP.NET Core docs repo before relying on memory.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    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.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    6/16 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub last month.

Activeupdated 9 months ago
  • 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

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.

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.