mcpField
D
dotnet-backend-patterns

dotnet-backend-patterns

github.com/sickn33Development49.1k302 installsUpdated today
Repository

About dotnet-backend-patterns

A guidance skill for C#/.NET developers building APIs, MCP servers, and backend services, with patterns for architecture, data access, testing, and reliability.

Key features

  1. 01API and MCP server patterns
  2. 02Dependency injection and layering
  3. 03Caching and data access guidance
  4. 04Testing and observability practices
  5. 05Error handling and resilience

Use cases

  1. 01Designing a .NET Web API
  2. 02Reviewing C# backend code
  3. 03Improving EF Core or Dapper access
  4. 04Adding tests to critical flows

MCP support

Covers patterns for building .NET MCP servers; it does not describe an MCP server or client.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-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/
service-template.cs.template
repository-template.cs.template
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

Template boundaries

Examples target .NET 8-era APIs and SQL Server; package/provider versions must be pinned and compiled in the destination application. Assets are partial sketches, not a standalone project: supply interfaces, DTO namespaces, options and schema. Use one shared domain Product type when combining them. Authorization/tenant filters precede reads, writes and cache access; the single-tenant sample keys are not suitable for multi-tenant data. No migration or production write is implied.

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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported