Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Coding
aspnet-core
Try itGet current, official-style ASP.NET Core guidance for building, refactoring, and upgrading .NET web apps.
What it does
A reference-driven guide for ASP.NET Core work that routes a task to the smallest set of focused documents: stack selection, Program.cs and the request pipeline, then exactly one app-model reference (Blazor, Razor Pages, MVC, or Minimal APIs/controllers), plus cross-cutting references for data, security, realtime, testing, and versioning. It states default assumptions such as preferring WebApplicationBuilder/WebApplication, built-in DI, options, logging, ProblemDetails, OpenAPI, health checks, rate limiting, and Identity before third-party infrastructure, and respecting the existing app model. It also points to a source map for finding the matching Microsoft Learn section.
When to use it
- Choosing between Blazor, Razor Pages, MVC, and Minimal APIs for a new app
- Structuring Program.cs, DI, configuration, and middleware in an existing solution
- Adding authentication, authorization, or Identity to a web app
- Planning a migration between ASP.NET Core major versions
The skill document
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
- Confirm the target framework, SDK, and current app model.
- Open references/stack-selection.md first for new apps or major refactors.
- Open references/program-and-pipeline.md next for
Program.cs, DI, configuration, middleware, routing, logging, and static assets. - 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
- 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
- Open references/versioning-and-upgrades.md before introducing new platform APIs into an older solution or when migrating between major versions.
- 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
WebApplicationBuilderandWebApplication. Avoid olderStartupandWebHostpatterns 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
- references/_sections.md: Quick index and reading order.
- references/stack-selection.md: Choose the right ASP.NET Core application model and template.
- references/program-and-pipeline.md: Structure
Program.cs, services, middleware, routing, configuration, logging, and static assets. - references/ui-blazor.md: Build Blazor Web Apps, choose render modes, and use components, forms, and JS interop correctly.
- references/ui-razor-pages.md: Build page-focused server-rendered apps with handlers, model binding, and conventions.
- references/ui-mvc.md: Build controller/view applications with clear separation of concerns.
- references/apis-minimal-and-controllers.md: Build HTTP APIs with Minimal APIs or controllers, including validation and response patterns.
- references/data-state-and-services.md: Use EF Core,
DbContext, options,IHttpClientFactory, session, temp data, and app state responsibly. - references/security-and-identity.md: Apply authentication, authorization, Identity, secrets, data protection, CORS, CSRF, and HTTPS guidance.
- references/realtime-grpc-and-background-work.md: Use SignalR, gRPC, and hosted services.
- references/testing-performance-and-operations.md: Add integration tests, browser tests, caching, compression, health checks, rate limits, and deployment concerns.
- references/versioning-and-upgrades.md: Handle target frameworks, breaking changes, obsolete APIs, and migrations.
- references/source-map.md: Map the official ASP.NET Core documentation tree to the references in this skill.
Execution Notes
- When generating new code, start from the correct
dotnet newtemplate 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.
Questions people ask
- Does it load every reference at once?
- No. The workflow says to load the smallest set that fits the task: stack selection and pipeline references first, then exactly one primary app-model reference, adding cross-cutting references only as needed.
- Which .NET version does it assume?
- It prefers the latest stable release and, as of March 2026, recommends .NET 10 / ASP.NET Core 10 for new production work, treating ASP.NET Core 11 as preview unless preview features are explicitly requested. Repositories or requests that pin an older target take precedence.
- Will it rewrite my Razor Pages app into MVC?
- No. The guidance is to respect the existing app model and not rewrite Razor Pages to MVC or controllers to Minimal APIs without a clear reason; existing solution conventions come first when editing.
Related skills
figma-use
OfficialRun JavaScript against the Figma Plugin API to create, edit, and inspect nodes in a Figma file.
cli-creator
OfficialTurn API docs, an OpenAPI spec, curl examples, or a script into an installable CLI with stable JSON output.
algorithmic-art
OfficialTurns a short art request into a written generative-art philosophy plus a runnable p5.js sketch with seed controls.
skill-creator
OfficialDraft a new agent skill, test it against real prompts, and iterate until it works.
cloudflare-deploy
OfficialDeploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
More from OpenAI
Browse all skillschatgpt-apps
OfficialScaffold and refactor ChatGPT Apps SDK projects that pair an MCP server with a widget UI.
figma-generate-design
OfficialBuild or update full Figma screens using your published design system's components, variables, and styles instead of hardcoded values.
figma-generate-library
OfficialTurn a codebase into a structured Figma design system, phase by phase, with your approval at each checkpoint.
figma-use
OfficialRun JavaScript against the Figma Plugin API to create, edit, and inspect nodes in a Figma file.
hatch-pet
OfficialTurn a concept, brand cue, or reference image into a validated Codex pet spritesheet and pet.json package.
imagegen
OfficialGenerate or edit raster images inside a coding session, from hero shots to transparent-background cutouts.