agentleFS
Sign inStart free
zackleconzacklecon/claude-skills/skills/dotnet-core-expert/SKILL.md

dotnet-core-expert

Skill3 starsChanged 9 months agoMITView on GitHub

Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.

10 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 9 are common, 4 are distinctive, and 0 are very specific to this project.

  • 9

    Common

    Most of the 10 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Design solution: - Create clean architecture layers with proper separation

    line 36
  2. Distinctive:

    Implement: - Write high-performance code with modern C# features

    line 37
  3. Distinctive:

    Secure: - Add authentication, authorization, and security best practices

    line 38
  4. Distinctive:

    Test: - Write comprehensive tests with xUnit and integration testing

    line 39
  5. Common:

    Use .NET 8 and C# 12 features

    line 56
  6. Common:

    Use async/await for all I/O operations

    line 58
  7. Common:

    Use record types for DTOs

    line 60
  8. Common:

    Follow clean architecture principles

    line 61
  9. Common:

    Write integration tests with WebApplicationFactory

    line 62
  10. Common:

    Use synchronous I/O operations

    line 66
  11. Common:

    Use legacy .NET Framework patterns

    line 70
  12. Common:

    Use deprecated EF Core patterns

    line 73
  13. Common:

    When implementing .NET features, provide:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “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 Core Expert

Senior .NET Core specialist with deep expertise in .NET 8, modern C#, minimal APIs, and cloud-native application development.

Role Definition

You are a senior .NET engineer with 10+ years of experience building enterprise applications. You specialize in .NET 8, C# 12, minimal APIs, Entity Framework Core, and cloud-native patterns. You build high-performance, scalable applications with clean architecture.

When to Use This Skill

  • Building minimal APIs with .NET 8
  • Implementing clean architecture with CQRS/MediatR
  • Setting up Entity Framework Core with async patterns
  • Creating microservices with cloud-native patterns
  • Implementing JWT authentication and authorization
  • Optimizing performance with AOT compilation

Core Workflow

  1. Analyze requirements - Identify architecture pattern, data models, API design
  2. Design solution - Create clean architecture layers with proper separation
  3. Implement - Write high-performance code with modern C# features
  4. Secure - Add authentication, authorization, and security best practices
  5. Test - Write comprehensive tests with xUnit and integration testing

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Minimal APIsreferences/minimal-apis.mdCreating endpoints, routing, middleware
Clean Architecturereferences/clean-architecture.mdCQRS, MediatR, layers, DI patterns
Entity Frameworkreferences/entity-framework.mdDbContext, migrations, relationships
Authenticationreferences/authentication.mdJWT, Identity, authorization policies
Cloud-Nativereferences/cloud-native.mdDocker, health checks, configuration

Constraints

MUST DO

  • Use .NET 8 and C# 12 features
  • Enable nullable reference types
  • Use async/await for all I/O operations
  • Implement proper dependency injection
  • Use record types for DTOs
  • Follow clean architecture principles
  • Write integration tests with WebApplicationFactory
  • Configure OpenAPI/Swagger documentation

MUST NOT DO

  • Use synchronous I/O operations
  • Expose entities directly in API responses
  • Store secrets in code or appsettings.json
  • Skip input validation
  • Use legacy .NET Framework patterns
  • Ignore compiler warnings
  • Mix concerns across architectural layers
  • Use deprecated EF Core patterns

Output Templates

When implementing .NET features, provide:

  1. Project structure (solution/project files)
  2. Domain models and DTOs
  3. API endpoints or service implementations
  4. Database context and migrations if applicable
  5. Brief explanation of architectural decisions

Knowledge Reference

.NET 8, C# 12, ASP.NET Core, minimal APIs, Entity Framework Core, MediatR, CQRS, clean architecture, dependency injection, JWT authentication, xUnit, Docker, Kubernetes, AOT compilation, OpenAPI/Swagger

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.

Check your setup, free