dotnet-backend-patterns

Design and review C# and .NET backend implementations with EF Core, Dapper, and xUnit.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill dotnet-backend-patterns-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-backend-patterns
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/dotnet-backend-patterns
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill dotnet-backend-patterns-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Helps teams build, review, and maintain production-grade C# and .NET backends without reinventing common architecture, data access, caching, and testing decisions.

Core Features & Use Cases

  • API and service design: Create clean, maintainable Web APIs and backend services with dependency injection, async workflows, and layered architecture.
  • Data access guidance: Choose between EF Core and Dapper, tune queries, manage repositories, and avoid common performance pitfalls.
  • Reliability and testing: Apply configuration patterns, caching strategies, validation, and xUnit-based unit or integration testing for safer releases.
  • Use case: A developer can use this Skill to design a new order API, optimize database queries, add cache invalidation, and structure tests for business rules.

Quick Start

Ask for a .NET backend implementation or review plan that covers architecture, data access, caching, configuration, and tests for your specific API.

Frequently Asked Questions about dotnet-backend-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a .NET backend with dependency injection and async workflows?

Build robust .NET backends by combining dependency injection, async/await workflows, and layered architecture to create maintainable Web APIs and enterprise services. This approach ensures clean separation of concerns and testable application architectures.

When should I use EF Core versus Dapper for data access in ASP.NET Core?

Choose between EF Core for rapid development with change tracking and complex mappings, or Dapper for high-performance lightweight queries. Evaluating your data access needs helps tune queries, manage repositories, and avoid common performance pitfalls.

What's the best way to configure and validate settings in an ASP.NET Core service?

The best way to configure ASP.NET Core services is using IOptions-based configuration patterns combined with validation. This ensures reliable application settings and caching strategies are correctly loaded and validated before runtime use.

How do I write xUnit tests for C# business rules and API endpoints?

Write xUnit tests for C# business rules by structuring unit and integration tests around your dependency-injected architecture. This pattern covers business logic validation and API endpoints to ensure safer releases.

Can I use this approach to add cache invalidation to an existing .NET Web API?

Yes, you can apply these .NET backend patterns to add cache invalidation to an existing Web API. The approach provides caching strategies and configuration patterns that integrate safely with your current architecture.