aspnet-minimal-api-openapi

Create ASP.NET Minimal API endpoints with typed results and OpenAPI documentation.

Updated May 16, 2026

Search Tags:#openapi #swagger #minimal api #asp.net #endpoint filters #typed results

Ready to run

npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill aspnet-minimal-api-openapi-p-o-ke-nae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aspnet-minimal-api-openapi
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/aspnet-minimal-api-openapi
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill aspnet-minimal-api-openapi-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design ASP.NET Minimal API endpoints that stay maintainable as they grow, while keeping request handling, responses, and API documentation consistent.

Core Features & Use Cases

Endpoint Organization: Group related routes with MapGroup, use endpoint filters, and split larger APIs into feature-focused endpoint classes.
Type-Safe Contracts: Define explicit request and response DTOs, use records and validation attributes, and return strongly typed results.
OpenAPI/Swagger Quality: Add summaries, descriptions, operation names, response metadata, and document or schema transformers for polished API docs.
Use Case: Build a clean product API for a web app where each feature exposes well-documented, discoverable endpoints with predictable errors and responses.

Quick Start

Ask for a well-structured ASP.NET Minimal API endpoint set for your feature, including DTOs, validation, typed results, and complete OpenAPI metadata.

Frequently Asked Questions about aspnet-minimal-api-openapi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add OpenAPI documentation to ASP.NET Minimal API endpoints?▼

To add OpenAPI documentation to ASP.NET Minimal API endpoints, you define summaries, descriptions, operation names, response metadata, and document or schema transformers directly on your endpoint configurations for polished API docs.

What is the best way to structure large Minimal APIs in ASP.NET?▼

The best way to structure large Minimal APIs in ASP.NET is to group related routes with MapGroup, apply endpoint filters, and split larger APIs into feature-focused endpoint classes for maintainability.

How do I return typed results and ProblemDetails in a Minimal API?▼

To return typed results and ProblemDetails in a Minimal API, use TypedResults or Results<T1, T2> for strongly typed route binding, and configure validation attributes on your request DTOs to generate predictable error responses.

Can I use feature-based endpoint classes with ASP.NET Minimal APIs?▼

Yes, you can use feature-based endpoint classes with ASP.NET Minimal APIs by splitting larger APIs into focused classes, organizing routes with MapGroup, and applying endpoint filters for consistent request handling.

How do Minimal APIs handle request and response DTO modeling for production?▼

Minimal APIs handle request and response DTO modeling for production by defining explicit DTOs using records, applying validation attributes, and returning strongly typed results to ensure type-safe contracts.

Why does my Minimal API Swagger documentation lack response metadata?▼

Your Minimal API Swagger documentation lacks response metadata because you need to explicitly configure OpenAPI summaries, descriptions, operation names, and schema transformers on your endpoints for complete API docs.