What problem does it solve? Building ASP.NET Core Web APIs involves many conventions that are easy to get wrong: correct HTTP status codes, DTO design, OpenAPI documentation, cancellation support, and centralized error handling. This Skill guides the creation and modification of Web API endpoints so they follow consistent HTTP semantics, proper OpenAPI metadata, and RFC 7807 Problem Details error responses. ## Core Features & Use Cases - Endpoint Implementation: Adds controller-based or minimal API endpoints matching the existing project style, with correct status codes (201 with Location header, 204 for deletes) and CancellationToken forwarding. - DTO and Validation Conventions: Defines sealed record request/response types with XML doc comments, DateTimeOffset for dates, string-serialized enums, and explicit validation registration for minimal APIs. - OpenAPI and Error Handling: Wires up built-in .NET 9+ OpenAPI support (avoiding Swashbuckle on modern targets), endpoint metadata, and a global IExceptionHandler returning Problem Details. - Use Case: Ask the assistant to add a CRUD endpoint for a Product resource to an existing minimal API project, and receive the endpoint, DTOs, service layer with interface, OpenAPI metadata, exception handler, and a .http test file, verified with a clean build. ## Quick Start Add a new REST endpoint for managing products to my ASP.NET Core project, including DTOs, OpenAPI documentation, error handling, and a .http test file.