dotnet-backend
Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.
Author
Category
Development ToolsInstall
Hot:44
Download and extract to your skills directory
Copy command and send to OpenClaw for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=sickn33-skills-dotnet-backend&locale=en&source=copy
.NET Backend Agent - ASP.NET Core Enterprise-level Backend Development Expert
Skills Overview
.NET Backend Agent is a .NET/C# backend development expert with 8+ years of experience, specialized in helping developers build high-performance, scalable, enterprise-grade ASP.NET Core API services.
Applicable Scenarios
1. Building ASP.NET Core Web APIs
Whether using the traditional Controller pattern or the modern Minimal API, it can help you quickly set up RESTful endpoints. Supports mainstream databases like SQL Server, PostgreSQL, and MySQL, and integrates Entity Framework Core for efficient data access.
2. Implementing a complete authentication and authorization system
From JWT token generation and validation, to ASP.NET Core Identity integration, and policy-based fine-grained authorization. Supports enterprise identity solutions such as OAuth 2.0 and Azure AD to ensure your APIs are secure and reliable.
3. Developing background services and scheduled jobs
Need to handle asynchronous tasks, scheduled jobs, or message queues? Use IHostedService and BackgroundService to build long-running services, or integrate Hangfire and Quartz.NET for professional task scheduling.
Core Features
Enterprise-grade API architecture design
Follows SOLID principles and best practices, implementing dependency injection, global exception handling, CORS configuration, response compression, health checks, and other production-level features. Supports API versioning, automatic Swagger/OpenAPI documentation generation, FluentValidation for complex validation, Serilog structured logging, and other modern development patterns.
Entity Framework Core data access
From DbContext configuration to Code First migrations, from Include/ThenInclude eager loading to AsNoTracking read-only query optimization. Proficient in mixed-use scenarios with micro-ORMs like Dapper to ensure the data access layer is high-performance and maintainable.
High-performance background services
Uses async/await asynchronous programming patterns combined with connection pooling, response caching, and .NET 8+ output caching to improve throughput. For complex business scenarios, supports CQRS + MediatR architecture patterns to achieve read-write separation and Domain-Driven Design.
Frequently Asked Questions
What important changes does ASP.NET Core 8 have compared to previous versions?
ASP.NET Core 8 introduced Output Caching replacing Response Caching, enhanced Minimal API capabilities, improved native AOT support, and boosted startup performance and runtime efficiency. It also offers better support for containerized deployments and cloud-native applications.
How should I choose between Minimal API and Controller API?
For simple scenarios, microservices, or BFF layers, Minimal API is more concise and efficient; for complex business logic and large projects that require clear layered architecture, Controller API provides better maintainability and testability. Both can coexist in the same project.
What are some optimization techniques for EF Core query performance?
Using AsNoTracking for read-only queries, properly using Include to avoid the N+1 problem, choosing appropriate loading strategies (Eager/Lazy/Explicit), using projection queries (Select) to reduce data transfer, and enabling query splitting are all effective ways to significantly improve EF Core query performance.
Does this skill support front-end development?
No. .NET Backend Agent focuses on backend service development and does not cover front-end technology stacks. If you need to handle both front-end and back-end, it is recommended to pair this with a dedicated front-end development skill.
Does it support older .NET Framework projects?
This skill primarily targets modern .NET (ASP.NET Core 8+). If you are maintaining a .NET Framework 4.x project, some patterns and best practices may not apply and will need to be adjusted based on the specific situation.