mcpField
D
dotnet-backend-patterns

dotnet-backend-patterns

github.com/rmyndharisDevelopment1.9k43 installsUpdated 2w ago
Repository

About dotnet-backend-patterns

.NET Backend Development Patterns is a skill for developers building .NET APIs, MCP servers, and backend services. It covers architecture, data access, resilience, testing, and observability, with a linked implementation playbook.

Key features

  1. 01Layered architecture and dependency injection
  2. 02Async and resilience patterns
  3. 03Redis caching and database access
  4. 04Testing and observability guidance

Use cases

  1. 01Designing a .NET Web API or MCP server
  2. 02Reviewing C# backend code
  3. 03Improving data access, caching, and reliability

MCP support

The skill provides guidance for developing .NET MCP servers. It does not specify server tools or resources.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rmyndharis/antigravity-skills --skill dotnet-backend-patterns

After installing, type/dotnet-backend-patternsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
repository-template.cs
service-template.cs
references/
dapper-patterns.md
ef-core-best-practices.md
resources/
implementation-playbook.md

Details

From the project README

.NET Backend Development Patterns

Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025).

Use this skill when

  • Developing new .NET Web APIs or MCP servers
  • Reviewing C# code for quality and performance
  • Designing service architectures with dependency injection
  • Implementing caching strategies with Redis
  • Writing unit and integration tests
  • Optimizing database access with EF Core or Dapper
  • Configuring applications with IOptions pattern
  • Handling errors and implementing resilience patterns

Do not use this skill when

  • The project is not using .NET or C#
  • You only need frontend or client guidance
  • The task is unrelated to backend architecture

Instructions

  • Define architecture boundaries, modules, and layering.
  • Apply DI, async patterns, and resilience strategies.
  • Validate data access performance and caching.
  • Add tests and observability for critical flows.
  • If detailed patterns are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed .NET patterns and examples.

Comments

Markdown supported