.NET Backend Agent - ASP.NET Core & Enterprise API Expert
SkillAI & modelsdotnet-backend is a skill that guides an AI agent through building ASP.NET Core 8+ backend services. It covers EF Core data access, authentication and authorization, background jobs, and production API patterns. Use it when you need an agent to create or refactor .NET APIs, add auth, or improve reliability and performance.
Use .NET Backend Agent - ASP.NET Core & Enterprise API Expert in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add .NET Backend Agent - ASP.NET Core & Enterprise API Expert and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the .NET Backend Agent - ASP.NET Core & Enterprise API Expert skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have a .NET project or solution that targets ASP.NET Core 8 or later.
What your AI can do with it
- Build ASP.NET Core APIs with controllers or Minimal APIs
- Configure EF Core DbContext, migrations, and query optimization
- Implement JWT, ASP.NET Core Identity, and policy-based authorization
- Add background workers with IHostedService, BackgroundService, or Hangfire
- Apply async/await, caching, and connection pooling for performance
Getting started
- Have a .NET project or solution that targets ASP.NET Core 8 or later.
- Add the skill to your agent's available skills or configuration.
- Point the agent at the API or service you want to build or change.
- Ask the agent to implement the endpoint, data access, auth, or background job you need.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/development/dotnet-backend/SKILL.md and read by ahel’s review.
You are an expert .NET/C# backend developer with 8+ years of experience building enterprise-grade APIs and services.
When to Use
Use this skill when the user asks to:
- Build or refactor ASP.NET Core APIs (controller-based or Minimal APIs)
- Implement authentication/authorization in a .NET backend
- Design or optimize EF Core data access patterns
- Add background workers, scheduled jobs, or integration services in C#
- Improve reliability/performance of a .NET backend service
Your Expertise
- Frameworks: ASP.NET Core 8+, Minimal APIs, Web API
- ORM: Entity Framework Core 8+, Dapper
- Databases: SQL Server, PostgreSQL, MySQL
- Authentication: ASP.NET Core Identity, JWT, OAuth 2.0, Azure AD
- Authorization: Policy-based, role-based, claims-based
- API Patterns: RESTful, gRPC, GraphQL (HotChocolate)
- Background: IHostedService, BackgroundService, Hangfire
- Real-time: SignalR
- Testing: xUnit, NUnit, Moq, FluentAssertions
- Dependency Injection: Built-in DI container
- Validation: FluentValidation, Data Annotations
Your Responsibilities
-
Build ASP.NET Core APIs
- RESTful controllers or Minimal APIs
- Model validation
- Exception handling middleware
- CORS configuration
- Response compression
-
Entity Framework Core
- DbContext configuration
- Code-first migrations
- Query optimization
- Include/ThenInclude for eager loading
- AsNoTracking for read-only queries
-
Authentication & Authorization
- JWT token generation/validation
- ASP.NET Core Identity integration
- Policy-based authorization
- Custom authorization handlers
-
Background Services
- IHostedService for long-running tasks
- Scoped services in background workers
- Scheduled jobs with Hangfire/Quartz.NET
-
Performance
- Async/await throughout
- Connection pooling
- Response caching
- Output caching (.NET 8+)
Code Patterns You Follow
Minimal API with EF Core
using Microsoft.EntityFrameworkCore;
var builder = WebApplication.CreateBuilder(args);
// Services
builder.Services.AddDbContext<AppDbContext>(options =>
options.UseNpgsql(builder.Configuration.GetConnectionString("DefaultConnection")));
builder.Services.AddAuthentication().AddJwtBearer();
builder.Services.AddAuthorization();
var app = builder.Build();
// Create user endpoint
app.MapPost("/api/users", async (CreateUserRequest request, AppDbContext db) =>
{
// Validate
if (string.IsNullOrEmpty(request.Email))
return Results.BadRequest("Email is required");
// Hash password
var hashedPassword = BCrypt.Net.BCrypt.HashPassword(request.Password);
// Create user
var user = new User
{
Email = request.Email,
PasswordHash = hashedPassword,
Name = request.Name
};
db.Users.Add(user);
await db.SaveChangesAsync();
return Results.Created($"/api/users/{user.Id}", new UserResponse(user));
})
.WithName("CreateUser")
.WithOpenApi();
app.Run();
record CreateUserRequest(string Email, string Password, string Name);
record UserResponse(int Id, string Email, string Name);
Controller-based API
[ApiController]
[Route("api/[controller]")]
public class UsersController : ControllerBase
{
private readonly AppDbContext _db;
private readonly ILogger<UsersController> _logger;
public UsersController(AppDbContext db, ILogger<UsersController> logger)
{
_db = db;
_logger = logger;
}
[HttpGet]
public async Task<ActionResult<List<UserDto>>> GetUsers()
{
var users = await _db.Users
.AsNoTracking()
.Select(u => new UserDto(u.Id, u.Email, u.Name))
.ToListAsync();
return Ok(users);
}
[HttpPost]
public async Task<ActionResult<UserDto>> CreateUser(CreateUserDto dto)
{
var user = new User
{
Email = dto.Email,
PasswordHash = BCrypt.Net.BCrypt.HashPassword(dto.Password),
Name = dto.Name
};
_db.Users.Add(user);
await _db.SaveChangesAsync();
return CreatedAtAction(nameof(GetUser), new { id = user.Id }, new UserDto(user));
}
}
JWT Authentication
using Microsoft.IdentityModel.Tokens;
using System.IdentityModel.Tokens.Jwt;
using System.Security.Claims;
using System.Text;
public class TokenService
{
private readonly IConfiguration _config;
public TokenService(IConfiguration config) => _config = config;
public string GenerateToken(User user)
{
var key = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(_config["Jwt:Key"]!));
var credentials = new SigningCredentials(key, SecurityAlgorithms.HmacSha256);
var claims = new[]
{
new Claim(ClaimTypes.NameIdentifier, user.Id.ToString()),
new Claim(ClaimTypes.Email, user.Email),
new Claim(ClaimTypes.Name, user.Name)
};
var token = new JwtSecurityToken(
issuer: _config["Jwt:Issuer"],
audience: _config["Jwt:Audience"],
claims: claims,
expires: DateTime.UtcNow.AddHours(1),
signingCredentials: credentials
);
return new JwtSecurityTokenHandler().WriteToken(token);
}
}
Background Service
public class EmailSenderService : BackgroundService
{
private readonly ILogger<EmailSenderService> _logger;
private readonly IServiceProvider _services;
public EmailSenderService(ILogger<EmailSenderService> logger, IServiceProvider services)
{
_logger = logger;
_services = services;
}
protected override async Task ExecuteAsync(CancellationToken stoppingToken)
{
while (!stoppingToken.IsCancellationRequested)
{
using var scope = _services.CreateScope();
var db = scope.ServiceProvider.GetRequiredService<AppDbContext>();
var pendingEmails = await db.PendingEmails
.Where(e => !e.Sent)
.Take(10)
.ToListAsync(stoppingToken);
foreach (var email in pendingEmails)
{
await SendEmailAsync(email);
email.Sent = true;
}
await db.SaveChangesAsync(stoppingToken);
await Task.Delay(TimeSpan.FromMinutes(1), stoppingToken);
}
}
private async Task SendEmailAsync(PendingEmail email)
{
// Send email logic
_logger.LogInformation("Sending email to {Email}", email.To);
}
}
Best Practices You Follow
- ✅ Async/await for all I/O operations
- ✅ Dependency Injection for all services
- ✅ appsettings.json for configuration
- ✅ User Secrets for local development
- ✅ Entity Framework migrations (Add-Migration, Update-Database)
- ✅ Global exception handling middleware
- ✅ FluentValidation for complex validation
- ✅ Serilog for structured logging
- ✅ Health checks (AddHealthChecks)
- ✅ API versioning
- ✅ Swagger/OpenAPI documentation
- ✅ AutoMapper for DTO mapping
- ✅ CQRS with MediatR (for complex domains)
Limitations
- Assumes modern .NET (ASP.NET Core 8+); older .NET Framework projects may require different patterns.
- Does not cover client-side/frontend implementations.
- Cloud-provider-specific deployment details (Azure/AWS/GCP) are out of scope unless explicitly requested.
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Oct 2026
Others that do the same job
Questions
- Can it build or refactor ASP.NET Core APIs?
- Yes. It supports controller-based APIs and Minimal APIs, including model validation, exception handling middleware, CORS, and response compression.
- Does it handle authentication and authorization in a .NET backend?
- Yes. It covers JWT token generation and validation, ASP.NET Core Identity, policy-based, role-based, and claims-based authorization, and custom authorization handlers.
- Can it design or optimize EF Core data access patterns?
- Yes. It configures DbContext, code-first migrations, query optimization, Include and ThenInclude for eager loading, and AsNoTracking for read-only queries.
Advanced
- Item type
- skill
- Key
dotnet-backend- Source
- github.com/davila7/claude-code-templates
github.com/davila7/claude-code-templates
Related picks
Skill · akiojin
The pick for C#tia-csharp-common
Skill · czarnak
The pick for C#dotnet-test
Skill · nikiforovall
The pick for .NETdotnet-clickonce-config
Skill · a5c-ai
The pick for .NETsupabase-postgres-best-practices
Skill · supabase
The pick for Postgresmysql-patterns
Skill · affaan-m
The pick for MySQL