Dotnet Core Expert

by jeffallan1be15d8064f8MIT11K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 days ago

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.

Instructions onlySoftware Development
AI-generated overview

Guides building .NET 8 applications with minimal APIs, clean architecture, EF Core, CQRS and JWT authentication.

What it does
Provides a workflow and reference guidance for implementing .NET 8 backend applications, covering minimal APIs, clean architecture layers, Entity Framework Core, authentication and cloud-native concerns. It supplies code examples for endpoints, MediatR query handlers, DbContext usage and record DTOs, and defines must-do and must-not-do constraints. Output is implementation code plus a brief explanation of architectural decisions.
When to use it
Use when building or extending .NET 8 or ASP.NET Core services, especially with minimal APIs, CQRS with MediatR, Entity Framework Core, or JWT authentication. Also suited to cloud-native microservice work such as Docker, health checks and configuration.
Requirements
Requires the .NET 8 SDK and C# 12 tooling, including dotnet build and dotnet test, plus xUnit and WebApplicationFactory for integration tests. Reference files are read by the model; no scripts are shipped.

.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

csharp
// Program.csvar 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

csharp
// Application/Users/GetUserQuery.cspublic 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

csharp
// Infrastructure/AppDbContext.cspublic 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 servicepublic 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

csharp
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

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Source and attribution

Source:jeffallan/claude-skillsinskills/dotnet-core-expertat commit1be15d8

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Dotnet Core Expert Agent Skill | SourceWeft