Creates ASP.NET Core Web API endpoints with OpenAPI metadata and error handling.
npx skills add https://github.com/FittyAr/Cardscape --skill dotnet-webapi-fittyar
Please help me install this Agent Skill. Skill: dotnet-webapi Source: https://github.com/FittyAr/Cardscape/tree/main/.agents/skills/dotnet-webapi Command: npx skills add https://github.com/FittyAr/Cardscape --skill dotnet-webapi-fittyar
TypedResults, and CancellationToken forwarding. - OpenAPI & DTO Conventions: Wires up built-in .NET 9+ OpenAPI support, XML doc comments, string enum serialization, and sealed record DTOs with validation. - Error Handling & Testing: Configures RFC 7807 Problem Details via IExceptionHandler middleware and generates .http request files for manual verification. - Use Case: Ask the AI to add a CRUD endpoint for a new Product resource, and it produces the DTOs, service layer with interface, minimal API mappings with OpenAPI metadata, global exception handling, and a .http test file that builds cleanly. ## Quick Start Add a new REST endpoint to my ASP.NET Core project for managing products, including DTOs, OpenAPI documentation, error handling, and a .http test file.High-intent search queries and answers about installing and using this skill.
First detect whether the project uses controllers or minimal APIs, then follow that style. Define sealed record request and response DTOs, implement the endpoint with correct status codes and CancellationToken, and add OpenAPI metadata like WithName, WithSummary, and Produces.
Match whatever style the project already uses and never mix both in one project. For brand-new projects, default to minimal APIs unless controllers are explicitly requested, organizing endpoints in static classes with a Map method per resource.
No. .NET 9 and later include built-in OpenAPI support via AddOpenApi() and MapOpenApi(), and Swashbuckle packages have known compatibility issues with these versions. Swashbuckle remains acceptable only for projects targeting .NET 8 or earlier.
The error occurs when TypedResults.Ok and TypedResults.NotFound appear in a ternary without an explicit return type, since they share no common base type. Annotate the handler with Task<Results<Ok<T>, NotFound>> so the compiler can infer the delegate correctly.
Register AddProblemDetails() and UseExceptionHandler(), then implement IExceptionHandler to map exception types to status codes and write RFC 7807 Problem Details JSON. Place the handler class in a Middleware folder and avoid leaking exception messages to clients.
It does not apply to gRPC services, SignalR hubs, Blazor or frontend work, or EF Core query optimization, which is covered by the optimizing-ef-core-queries skill. It also excludes general C# style questions unrelated to HTTP APIs.
jim60105Scaffold EF Core DbContext and entity models from existing databases.
blockmaticGenerate TypeScript clients from OpenAPI 3.0 specs with Zod validation.
diegoknskConfigure EF Core repositories, DbContext, and migrations for data access.
rudironsoniImplement real-time communication patterns in .NET with SignalR, SSE, JSON-RPC 2.0, and gRPC streaming.