domains / families / software-engineering / dotnet-webapi

dotnet-webapi

separate

Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.

When to use

• adding or modifying Web API endpoints implemented with controllers or minimal APIs;
• wiring up OpenAPI/Swagger metadata and endpoint documentation;
• defining request/response DTOs and consistent HTTP status code behavior;
• adding `.http` files or similar request-based API testing artifacts;
• configuring centralized API error handling middleware or exception mapping.

When not to use

• general C# coding style or non-API refactoring;
• EF Core data modeling or query optimization work; use `optimizing-ef-core-queries`;
• frontend, Razor, or Blazor UI changes;
• gRPC services;
• SignalR hubs or real-time messaging flows.

Skill page

Source