dotnet-backend-patterns

الگوهای C#/.NET برای API، سرور MCP و backend سازمانی

این اسکیل الگوهای C#/.NET مدرن را برای API تولیدی، سرور MCP و backend سازمانی ارائه می‌دهد.

چه چیزی می‌گیرید

  • الگوهای API
  • سرور MCP
  • مرزهای قالب

برای چه کاری خوب است

  • backend سازمانی
  • ساخت MCP در .NET

برای چه کاری نیست

  • پروژه‌های غیر .NET

دربارهٔ این اسکیل

.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.

دانلود ZIP