minimal-apis
FeaturedDesign and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- managedcode
- Repository
- managedcode/dotnet-skills
- Created
- 6 months ago
- Last Updated
- 6 days ago
- Language
- C#
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
aspnet-minimal-api
ASP.NET Core Minimal API endpoints, route groups, filters, and typed results. Covers modern .NET 8+ endpoint patterns. USE WHEN: user mentions "Minimal API", "MapGet", "MapPost", "route groups", "endpoint filters", ".NET minimal", "lambda endpoints" DO NOT USE FOR: Controller-based APIs (use `aspnet-core`), Express.js (use `express`), FastAPI (use `fastapi`)
neo-dotnet-minimal-apis
Use this skill when building, debugging, refactoring, or reviewing ASP.NET Core Minimal APIs, lightweight endpoints, route groups, endpoint filters, typed results, OpenAPI metadata, or high-performance .NET API services without controllers.
aspnet-api-patterns
ASP.NET Core API patterns — controllers vs minimal API, middleware, error handling, versioning, and authentication setup.