Group .NET 10 Minimal API routes into discoverable IEndpointGroup modules.
npx skills add https://github.com/shahdanish/vibepos --skill minimal-api-shahdanish
Please help me install this Agent Skill. Skill: minimal-api Source: https://github.com/shahdanish/vibepos/tree/main/skills/minimal-api Command: npx skills add https://github.com/shahdanish/vibepos --skill minimal-api-shahdanish
It solves the problem of writing HTTP endpoints with scattered routing code by providing a consistent, scalable Minimal API pattern that preserves maintainability and produces accurate OpenAPI metadata.
MapGroup: Organize related routes into coherent feature files rather than spreading MapGet/MapPost calls across Program.cs.IEndpointGroup: Keep Program.cs stable while endpoint features are added or changed in isolation.TypedResults: Generate correct OpenAPI schemas while retaining compile-time safety for success/error response shapes.[AsParameters]), and capabilities such as OpenAPI, rate limiting, and output caching in a predictable way.OrderEndpoints group in a dedicated file and automatically register Create/List/Get endpoints with consistent response typing and documented metadata.Load this skill, then design each feature’s endpoints as an IEndpointGroup in its own file and register everything with a single app.MapEndpoints() call so OpenAPI and routing stay correct as the API grows.
High-intent search queries and answers about installing and using this skill.
Organize .NET minimal API endpoints by grouping related routes into feature files using MapGroup and auto-discovering them via IEndpointGroup, keeping Program.cs stable. This prevents routing sprawl by isolating endpoint registration into modular, maintainable structures.
Generate accurate OpenAPI schemas by using TypedResults union return types for compile-time safety and endpoint metadata methods. This approach ensures correct OpenAPI generation for success and error response shapes in .NET 10 HTTP APIs without requiring manual schema definitions.
The best way to structure a scalable .NET 10 HTTP API is applying a Minimal API endpoint architecture that groups routes into discoverable feature modules. Using IEndpointGroup auto-discovery and a single app.MapEndpoints() call ensures routing and OpenAPI stay correct as the API grows.
Yes, you can add rate limiting and output caching to .NET minimal API endpoints. The architecture supports production-ready cross-cutting features by applying endpoint filters and metadata methods predictably alongside parameter binding for robust HTTP API capabilities.
Parameter binding with [AsParameters] in .NET minimal APIs allows binding complex objects from multiple route, query, and body parameters. This is applied predictably alongside endpoint filters and metadata methods to handle inputs in scalable endpoint architectures.
You need IEndpointGroup to keep Program.cs stable while endpoint features are added or changed in isolation. It enables auto-discovery of route groups, preventing scattered routing code and ensuring maintainability as your .NET 10 HTTP API expands.
ojrojasAutomate migration of .NET 9 projects to .NET 10 with breaking changes.
codewithmukeshConfigure type-safe .NET 10 minimal API endpoints with TypedResults and endpoint filters.
rudironsoniDevelop ASP.NET Core Minimal APIs with lambda-based endpoints and TypedResults.
JaguarJackGenerate Laravel FormRequest validators for CatchAdmin module controllers.