Standardize .NET 10 Minimal API endpoints with MapGroup and TypedResults.
npx skills add https://github.com/Resgrid/Core --skill minimal-api-resgrid
Please help me install this Agent Skill. Skill: minimal-api Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/minimal-api Command: npx skills add https://github.com/Resgrid/Core --skill minimal-api-resgrid
It helps you build consistent, well-documented .NET 10 Minimal APIs without turning Program.cs into a growing tangle of scattered endpoint mappings.
IEndpointGroup endpoint groups via a single app.MapEndpoints() call so adding features doesn’t require editing Program.cs.TypedResults with explicit union return types to generate accurate Swagger/OpenAPI schemas.MapGroup, endpoint filters, parameter binding patterns, and built-in OpenAPI configuration to keep APIs maintainable and consistent.Use the minimal-api skill to structure your HTTP endpoints by creating IEndpointGroup files and registering them through app.MapEndpoints() so OpenAPI and routing metadata stay correct as the API grows.
High-intent search queries and answers about installing and using this skill.
To organize .NET minimal APIs cleanly, implement IEndpointGroup classes and register them through a single app.MapEndpoints() call. This auto-discovery approach keeps Program.cs tidy by ensuring new endpoint features never require manual route registration edits.
Generate accurate OpenAPI schemas for minimal APIs by using TypedResults with explicit union return types in your endpoint handlers. This type-safe response mechanism ensures deterministic Swagger documentation without requiring manual schema configuration.
Structure cross-cutting concerns in minimal APIs by applying endpoint filters, rate limiting, and output caching directly to MapGroup instances. Grouping endpoints this way allows shared policies to cascade across nested routes for consistent API behavior.
Yes, minimal APIs in .NET 10 support parameter binding for route, query, header, body, and dependency injection parameters. This built-in binding capability automatically maps HTTP request data to your endpoint method signatures for streamlined request handling.
Yes, attaching endpoint metadata like WithName, WithTags, and WithSummary is required for minimal APIs to ensure deterministic behavior and OpenAPI discoverability. These annotations provide the necessary routing and documentation context for Swagger generation.
MudraMartinOrganizes service registrations in ASP.NET Core via reusable extension methods.
teexiiiServe interactive Swagger UI and raw OpenAPI spec from a TypeScript-based definition.
fgarofalo56Develop .NET 8+ backend services with C#, ASP.NET Core, and Entity Framework Core.
microsoftConvert ASP.NET MVC RouteCollection routing to ASP.NET Core endpoint routing.