agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-dotnet-minimal-apis/SKILL.md

neo-dotnet-minimal-apis

Skill7 starsChanged 6 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check .csproj to identify TargetFramework.

    line 23
  2. Distinctive:

    Write clean, high-performance Minimal API code, prioritizing Lambdas or extension methods.

    line 31
  3. Distinctive:

    Check whether the generated OpenAPI documentation is complete.

    line 36
  4. Very specific:

    Ensure asynchronous operations correctly pass the CancellationToken.

    line 37
  5. Very specific:

    Route Groups: Use MapGroup to consolidate prefixes and authentication.

    line 43
  6. Very specific:

    Async Safety: Always accept and pass down CancellationToken.

    line 66
  7. Distinctive:

    Ensure the provided code executes correctly in a .NET 6+ environment.

    line 75
  8. Distinctive:

    Check if the code complies with high-performance best practices for Minimal APIs (e.g., avoiding closures, reducing allocations).

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

.NET Minimal APIs Expert Skill

Trigger On

  • The user requests to create, debug, refactor, or review .NET Minimal APIs.
  • The project's Program.cs contains WebApplication.CreateBuilder(args) and is not configured with a Controllers directory.
  • The target framework is .NET 6.0 (LTS) and above.
  • There is a need to optimize API performance or simplify Web API architecture.

Workflow

  1. Perceive (Architecture Awareness):
    • Check .csproj to identify TargetFramework.
    • Analyze Program.cs to distinguish whether it uses simple endpoints or adopts a Module-based or Vertical Slice organization.
    • Identify whether OpenAPI (Swagger) support has been configured.
  2. Reason (Planning Phase):
    • Evaluate whether "Route Groups" need to be introduced to optimize organizational structure.
    • Determine whether to use "Endpoint Filters" to handle cross-cutting concerns (such as parameter validation).
    • Choose the most appropriate syntax based on the .NET version (e.g., TypedResults in .NET 7+).
  3. Act (Execution Phase):
    • Write clean, high-performance Minimal API code, prioritizing Lambdas or extension methods.
    • Implement strong typing and DTOs (prioritize using record).
    • Integrate dependency injection, avoiding the Service Locator pattern.
  4. Validate (Standard Validation):
    • Validate whether the endpoints correctly return expected HTTP status codes.
    • Check whether the generated OpenAPI documentation is complete.
    • Ensure asynchronous operations correctly pass the CancellationToken.

Feature Roadmap (.NET 6 - 11)

.NET 6 & 7 (Foundation)

  • Minimal Hosting: Simplified startup process and top-level statements.
  • Route Groups: Use MapGroup to consolidate prefixes and authentication.
  • Endpoint Filters: Implement interception logic within Minimal APIs.
  • Typed Results: Improved unit testing and Swagger support.

.NET 8 & 9 (Productivity)

  • Antiforgery: Built-in anti-forgery token support.
  • Form Binding: Support for [FromForm] parameter binding.
  • HybridCache: High-performance multi-level caching support.
  • OpenAPI Improvements: Better OpenAPI code generation.

.NET 10 (AOT & Middleware)

  • Native AOT Optimization: AOT-optimized compilation tailored for Minimal APIs.
  • Enhanced Middleware Patterns: New middleware designed for lightweight architectures.

.NET 11+ (Version-Specific Features)

  • Asynchronous Validation Support: Native async validation rules across Minimal API endpoints and parameter binding, awaiting validation logic seamlessly.
  • OpenAPI 3.2 by Default: Updated default specification to OpenAPI 3.2, with support for OpenApiGenerationEnvironment in build-time generation.
  • Zstandard (zstd) Compression: Native high-ratio, low-latency compression provider for response compression and request decompression.
  • Runtime Async Performance: Reduced task state machine allocations and cleaner async stack traces across endpoint handlers.

Coding Standards

  • Clean Routing: Prioritize using extension methods to modularize routes.
  • Strong Typing: Prioritize using TypedResults and Results<T1, T2>.
  • Async Safety: Always accept and pass down CancellationToken.
  • DI Best Practices: Services should be defined directly in the Handler parameters.

Deliver

  • Version-Optimized API Code: Provide the most appropriate modern API code based on the target .NET version.
  • Modular Architecture: Provide structural suggestions for extracting Program.cs routes into extension methods.
  • OpenAPI Configuration: Provide comprehensive Swagger/OpenAPI configuration suggestions.

Validate

  • Ensure the provided code executes correctly in a .NET 6+ environment.
  • Validate endpoint security (authentication, authorization, Antiforgery).
  • Check if the code complies with high-performance best practices for Minimal APIs (e.g., avoiding closures, reducing allocations).

Documentation

Official References

Internal References

  • Minimal APIs Coding Style and Naming Conventions
  • Minimal APIs Anti-Patterns and Best Practices
  • Minimal APIs Modern Patterns Guide

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.