agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-dotnet-webapi/SKILL.md

neo-dotnet-webapi

Skill7 starsChanged 6 months agoMITView on GitHub

Use this skill when building, debugging, refactoring, or reviewing controller-based ASP.NET Core Web APIs, including ControllerBase, ActionResult<T>, Problem Details, API versioning, global exception handling, DTOs, and OpenAPI behavior.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Write high-quality controllers compliant with [ApiController] conventions.

    line 31
  3. Distinctive:

    Check NRT (Nullable Reference Types) safety.

    line 36
  4. Very specific:

    Ensure asynchronous operations correctly pass down CancellationToken.

    line 37
  5. Very specific:

    Async Best Practices: Always accept and pass CancellationToken.

    line 66
  6. Distinctive:

    Ensure the code complies with C# 10+ modern syntax standards.

    line 75

≈ “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 Web API Expert Skill

Trigger On

  • The user requests to create, debug, refactor, or review ASP.NET Core Web APIs.
  • The project contains a Controllers directory and inherits from ControllerBase.
  • The target framework is .NET 6.0 (LTS) and above.
  • There is a need for API code modernization (e.g., migrating from Middleware exception handling to .NET 8+ IExceptionHandler).

Workflow

  1. Perceive (Architecture Awareness):
    • Check .csproj to identify TargetFramework.
    • Analyze project structure to confirm whether it uses N-Tier architecture or Vertical Slice.
    • Identify existing cross-cutting concern handling methods (filters, middleware).
  2. Reason (Planning Phase):
    • Evaluate whether to introduce the "Problem Details" standard.
    • Determine whether to use the .NET 8+ global exception handling mechanism.
    • Choose an appropriate versioning strategy based on project scale.
  3. Act (Execution Phase):
    • Write high-quality controllers compliant with [ApiController] conventions.
    • Implement strongly-typed and immutable DTOs (prioritize record).
    • Integrate dependency injection, prioritizing Primary Constructors (C# 12+).
  4. Validate (Standard Validation):
    • Validate whether Action return types comply with ActionResult<T> specifications.
    • Check NRT (Nullable Reference Types) safety.
    • Ensure asynchronous operations correctly pass down CancellationToken.

Feature Roadmap (.NET 6 - 11)

.NET 6 & 7 (Foundation)

  • Controllers Architecture: Traditional controller patterns and attribute routing.
  • Problem Details: Unified error response standards.
  • Output Caching: High-performance server-side caching.
  • Nullable Reference Types: Comprehensive null safety support.

.NET 8 & 9 (Productivity)

  • IExceptionHandler: More elegant centralized exception handling.
  • Antiforgery: Built-in anti-forgery support for Web APIs.
  • Keyed Services: More flexible dependency injection options.
  • HybridCache: Multi-level caching optimization.

.NET 10 (Extensions & Serialization)

  • Extension Members for Controllers: Extending base controller functionality.
  • Enhanced Serialization: JSON optimization for large payloads.

.NET 11+ (Version-Specific Features)

  • OpenAPI 3.2 Specification by Default: Upgraded documentation standards with enhanced schema generation.
  • Zstandard (zstd) Compression: Native high-speed, high-ratio compression via ZstandardCompressionProviderOptions.
  • TLS Channel Binding for Negotiate Authentication: Enhanced transport security for Kerberos / NTLM multi-round auth.
  • Runtime Async Controller Execution: Reduced Task allocation overhead and cleaner stack traces during controller action execution.

Coding Standards

  • Strong Typing: Prioritize ActionResult<T> to improve Swagger support.
  • NRT Compliance: Strictly enforce Null safety to reduce runtime errors.
  • Async Best Practices: Always accept and pass CancellationToken.
  • Naming: Controller names must end with Controller, async methods must end with Async.

Deliver

  • Version-Optimized Web API Code: Provide modernized controllers and configurations suitable for the target version.
  • Architectural Insights: Provide refactoring suggestions for N-Tier or Clean Architecture.
  • Security Recommendations: Provide security suggestions regarding Problem Details and exception handling.

Validate

  • Ensure the code complies with C# 10+ modern syntax standards.
  • Validate endpoints correctly return error formats compliant with RFC 7807.
  • Confirm the code has no resource leaks in the tested environment (correct use of using and async).

Documentation

Official References

Internal References

  • Web API Coding Style and Naming Conventions
  • Web API Anti-Patterns and Best Practices
  • Web API 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.