api

Standardize .NET Minimal API endpoints with vertical slicing and OpenAPI metadata.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill api-a35506322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/api
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill api-a35506322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent implementation patterns and missing standards when developing .NET Minimal API backend projects, ensuring team-wide code consistency and reducing debugging time from non-compliant implementations.

Core Features & Use Cases

  • Vertical Slicing Structure: Enforces a modular folder layout organized by feature for endpoints, models, and example providers to keep code maintainable.
  • Database Optimization: Provides guidelines for EF Core query optimization, Dapper integration, transaction management, and N+1 query prevention to improve performance.
  • Standardized API Patterns: Includes rules for OpenAPI metadata documentation, unified exception handling, and third-party API adapter implementation to ensure consistent API behavior.
  • Use Case: Use this Skill when building a new .NET backend API to ensure all endpoints follow consistent naming, documentation, and error response patterns from the start of development.

Quick Start

Use the api skill to implement a new user login endpoint that follows the project's vertical slicing, OpenAPI documentation, and unified error response standards.

Frequently Asked Questions about api

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

FAQPage Schema
How do I structure a .NET Minimal API project to ensure team-wide code consistency?

To structure a .NET Minimal API project for consistency, enforce a vertical slicing folder layout organized by feature for endpoints, models, and example providers. This modular structure keeps code maintainable and eliminates inconsistent implementation patterns across backend development teams.

What is the best way to optimize EF Core queries and prevent N+1 issues in Minimal APIs?

The best way to optimize EF Core queries and prevent N+1 issues in Minimal APIs is to apply specific database optimization guidelines. These include leveraging Dapper integration for mixed queries, enforcing transaction management, and following structured query performance rules.

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

To add OpenAPI metadata documentation to .NET Minimal API endpoints, apply standardized API patterns that enforce compliance rules for endpoint documentation. This ensures consistent API behavior and unified error response patterns across the entire backend implementation.

Can I use Dapper alongside EF Core for database queries in a .NET backend?

Yes, you can use Dapper alongside EF Core for database queries in a .NET backend. This mixed query approach improves performance by combining EF Core's query capabilities with Dapper's efficiency, while structured transaction management ensures data integrity.

How do I implement unified exception handling and third-party API adapters in Minimal APIs?

To implement unified exception handling and third-party API adapters in Minimal APIs, apply standardized API patterns that include structured HTTP client resilience configuration. This ensures consistent API behavior, reliable external integrations, and unified error responses across endpoints.