aspnet-minimal-api

Implement ASP.NET Core Minimal API endpoints with .NET 8 best practices.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Szantoi/spaceos-modules-cabinet --skill aspnet-minimal-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspnet-minimal-api
Source: https://github.com/Szantoi/spaceos-modules-cabinet/tree/main/.claude/skills/aspnet-minimal-api
Command: npx skills add https://github.com/Szantoi/spaceos-modules-cabinet --skill aspnet-minimal-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to implementing best practices for ASP.NET Core Minimal API in .NET 8, streamlining endpoint development and ensuring adherence to SpaceOS.Kernel API layer conventions.

Core Features & Use Cases

  • Minimal API Best Practices: Offers authoritative patterns for Minimal API endpoints, route groups, IResult returns, and more.
  • SpaceOS.Kernel API Conventions: Covers kebab-case routes, plural nouns, Result<T> mapping, and 201 Created with Location header.
  • Use Case: Ideal for developers building or reviewing Minimal API endpoints within the SpaceOS.Kernel.Api project.

Quick Start

Apply the aspnet-minimal-api skill to ensure your Minimal API endpoints follow SpaceOS.Kernel API layer conventions and best practices.

Frequently Asked Questions about aspnet-minimal-api

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

FAQPage Schema
How do I implement ASP.NET Core Minimal API best practices in .NET 8?

Implement ASP.NET Core Minimal API best practices by following patterns for endpoint design, IResult usage, MediatR integration, and route conventions to ensure consistent and maintainable code.

What are the route conventions for Minimal API endpoints in the SpaceOS.Kernel Api layer?

Minimal API route conventions for the SpaceOS.Kernel Api layer require kebab-case routes and plural nouns to ensure endpoint paths are consistent and maintainable.

How do I return 201 Created with Location header in a Minimal API endpoint?

Return 201 Created with a Location header in Minimal API endpoints by mapping Result<T> objects to IResult responses, adhering to standard API layer conventions.

Can I integrate MediatR with Minimal API endpoints in ASP.NET Core?

Yes, you can integrate MediatR with Minimal API endpoints in ASP.NET Core to handle commands and queries, streamlining endpoint development and enforcing maintainable architecture.

Does this Minimal API guide work with .NET 8 and SpaceOS.Kernel conventions?

Yes, this guide specifically targets .NET 8 and adapts to SpaceOS.Kernel API layer conventions, making it ideal for developers building or reviewing Minimal API endpoints within that project.