Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Dotnet Core Expert

  • 3.5k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

dotnet-core-expert is an agent skill for build .net 8 minimal apis with ef core, cqrs mediatr, jwt auth, and cloud-native microservice patterns.

About

The dotnet-core-expert skill 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. 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; run dotnet build to verify compilation if build fails, review errors, fix issues, and rebuild before proceeding 4. Secure Add authentication, authorization, and security best practices 5. Test Write comprehensive tests with xUnit and integration testing; run dotnet test to confirm all tests pass if tests fail, diagnose failures, fix the implementation, and re-run before continuing; verify endpoints with curl or a REST client Topic Reference Load When ------- ----------- ----------- Minimal APIs references/minimal-apis.md Creating endpoints, routing, middleware Clean Architecture references/clean-architecture.m

  • Analyze requirements — Identify architecture pattern, data models, API design
  • Design solution — Create clean architecture layers with proper separation
  • Secure — Add authentication, authorization, and security best practices
  • Use .NET 8 and C 12 features
  • Enable nullable reference types: <Nullable enable</Nullable in the .csproj

Dotnet Core Expert by the numbers

  • 3,549 all-time installs (skills.sh)
  • +92 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #4 of 154 .NET & C# skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

dotnet-core-expert capabilities & compatibility

Capabilities
analyze requirements — identify architecture pat · design solution — create clean architecture laye · secure — add authentication, authorization, and · use .net 8 and c 12 features · enable nullable reference types: <nullable enabl
Use cases
api development · devops
From the docs

What dotnet-core-expert says it does

1. **Analyze requirements** — Identify architecture pattern, data models, API design
SKILL.md
2. **Design solution** — Create clean architecture layers with proper separation
SKILL.md
3. **Implement** — Write high-performance code with modern C# features; run `dotnet build` to verify compilation — if build fails, review errors, fix issues, and rebuild before proceeding
SKILL.md
npx skills add https://github.com/jeffallan/claude-skills --skill dotnet-core-expert

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs3.5k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

How do I build .net 8 minimal apis with ef core, cqrs mediatr, jwt auth, and cloud-native microservice patterns with documented agent guidance?

Build .NET 8 minimal APIs with EF Core, CQRS MediatR, JWT auth, and cloud-native microservice patterns.

Who is it for?

Developers who need .net & c# help during build work.

Skip if: Skip when the task falls outside .NET & C# scope described in SKILL.md.

When should I use this skill?

Build .NET 8 minimal APIs with EF Core, CQRS MediatR, JWT auth, and cloud-native microservice patterns.

What you get

Completed .net & c# workflow aligned with SKILL.md steps and validation.

  • Minimal API Program.cs and endpoint maps
  • EF Core entities and DbContext
  • MediatR CQRS command and query handlers

By the numbers

  • Analyze requirements — Identify architecture pattern, data models, API design
  • Design solution — Create clean architecture layers with proper separation
  • Secure — Add authentication, authorization, and security best practices

Files

SKILL.mdMarkdownGitHub ↗

.NET Core Expert

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; run dotnet build to verify compilation — if build fails, review errors, fix issues, and rebuild before proceeding 4. Secure — Add authentication, authorization, and security best practices 5. Test — Write comprehensive tests with xUnit and integration testing; run dotnet test to confirm all tests pass — if tests fail, diagnose failures, fix the implementation, and re-run before continuing; verify endpoints with curl or a REST client

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: <Nullable>enable</Nullable> in the .csproj
  • Use async/await for all I/O operations — e.g., await dbContext.Users.ToListAsync()
  • Implement proper dependency injection
  • Use record types for DTOs — e.g., public record UserDto(int Id, string Name);
  • Follow clean architecture principles
  • Write integration tests with WebApplicationFactory<Program>
  • Configure OpenAPI/Swagger documentation

MUST NOT DO

  • Use synchronous I/O operations
  • Expose entities directly in API responses
  • Skip input validation
  • Use legacy .NET Framework patterns
  • Mix concerns across architectural layers
  • Use deprecated EF Core patterns

Code Examples

Minimal API Endpoint

// Program.cs
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();
builder.Services.AddMediatR(cfg => cfg.RegisterServicesFromAssembly(typeof(Program).Assembly));

var app = builder.Build();
app.UseSwagger();
app.UseSwaggerUI();

app.MapGet("/users/{id}", async (int id, ISender sender, CancellationToken ct) =>
{
    var result = await sender.Send(new GetUserQuery(id), ct);
    return result is null ? Results.NotFound() : Results.Ok(result);
})
.WithName("GetUser")
.Produces<UserDto>()
.ProducesProblem(404);

app.Run();

MediatR Query Handler

// Application/Users/GetUserQuery.cs
public record GetUserQuery(int Id) : IRequest<UserDto?>;

public sealed class GetUserQueryHandler : IRequestHandler<GetUserQuery, UserDto?>
{
    private readonly AppDbContext _db;

    public GetUserQueryHandler(AppDbContext db) => _db = db;

    public async Task<UserDto?> Handle(GetUserQuery request, CancellationToken ct) =>
        await _db.Users
            .AsNoTracking()
            .Where(u => u.Id == request.Id)
            .Select(u => new UserDto(u.Id, u.Name))
            .FirstOrDefaultAsync(ct);
}

EF Core DbContext with Async Query

// Infrastructure/AppDbContext.cs
public sealed class AppDbContext(DbContextOptions<AppDbContext> options) : DbContext(options)
{
    public DbSet<User> Users => Set<User>();

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.ApplyConfigurationsFromAssembly(typeof(AppDbContext).Assembly);
    }
}

// Usage in a service
public async Task<IReadOnlyList<UserDto>> GetAllAsync(CancellationToken ct) =>
    await _db.Users
        .AsNoTracking()
        .Select(u => new UserDto(u.Id, u.Name))
        .ToListAsync(ct);

DTO with Record Type

public record UserDto(int Id, string Name);
public record CreateUserRequest(string Name, string Email);

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

Documentation

Related skills

How it compares

dotnet-core-expert is an agent skill for build .net 8 minimal apis with ef core, cqrs mediatr, jwt auth, and cloud-native microservice patterns, not a generic alternative.

FAQ

Who is dotnet-core-expert for?

Developers using .NET & C# workflows with agent-guided SKILL.md steps.

When should I use dotnet-core-expert?

Build .NET 8 minimal APIs with EF Core, CQRS MediatR, JWT auth, and cloud-native microservice patterns.

Is dotnet-core-expert safe to install?

Review the Security Audits panel on this page before installing in production.

.NET & C#backend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.