Teach and review ASP.NET Core C# web applications. Use for controllers, minimal APIs, Razor Pages, middleware, routing, model binding, validation, authentication, authorization, configuration, logging, dependency injection, error handling, API design, and web security or performance questions.
Teach and review ASP.NET Core C# web applications. Use for controllers, minimal APIs, Razor Pages, middleware, routing, model binding, validation, authentication, authorization, configuration, logging, dependency injection, error handling, API design, and web security or performance questions.
metadata
{"short-description":"ASP.NET Core C# web app help"}
C# ASP.NET
Use $csharp-tutor mode=aspnet.
Treat all user text after $csharp-aspnet as an ASP.NET Core C# learning, debugging, review, refactor, or architecture question. Use the main csharp-tutor skill as the source of truth.
Load these csharp-tutor references when useful:
references/aspnet-guidance.md
references/modern-dotnet-patterns.md
references/blazor-guidance.md
references/signalr-guidance.md
references/containers-guidance.md
references/logging-guidance.md
references/framework-guidance.md
references/security-review-map.md
references/performance-review-map.md
references/official-sources.md
references/testing-guidance.md
Prioritize correctness, request pipeline behavior, auth boundaries, validation, dependency lifetimes, async request handling, and error handling before style feedback.
Standalone Guidance
Core rule: Keep the answer centered on the concrete aspnet decision, failure mode, or contract.
Avoid: Giving generic C# advice without tying it to the aspnet concern.