Automated summary
This skill guides the application of modern C#/.NET backend patterns to build robust APIs, MCP servers, and enterprise applications.
Strengths
- Spans a wide surface: async/await, dependency injection, EF Core, Dapper, IOptions configuration, Redis caching, and xUnit testing
- Enforces architecture scoping (modules, layering, resilience) before diving into code
- Points to a detailed playbook for deeper implementation patterns
- Includes validation of data-access performance and caching strategies
Limitations
- Content is largely high-level; concrete examples depend on the referenced resources/implementation-playbook.md, which is not included here
- Covers backend only, with no frontend or client guidance
- Assumes prior familiarity with the .NET ecosystem and tooling
Use it when starting or reviewing a .NET/C# backend: Web API, MCP server, service architecture, data access, or testing.
Skip it if the project is not .NET/C# or if the task is purely frontend or unrelated to backend architecture.
Security analysis
SafeThe skill is purely instructional documentation for C#/.NET backend patterns. It declares no tools, requests no credentials, runs no commands, and contains no destructive, exfiltrating, or obfuscated behavior.
No concerns found
How this analysis is madeExamples
Help me design the architecture for a new .NET 8 Web API with layered modules, dependency injection, and EF Core data access.Review this C# service class for async/await correctness, DI usage, and EF Core query performance issues.Add a Redis caching strategy and xUnit integration tests for this .NET endpoint that queries orders via Dapper.name: dotnet-backend-patterns description: Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.
.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.mdfor detailed .NET patterns and examples.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/net-backend-development-patterns-mryiqhtm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/net-backend-development-patterns-mryiqhtm/download' --output '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md.part' && mv '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md.part' '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && test -s '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dotnet-backend-patterns' && cp -R '.skill-downloads/net-backend-development-patterns-mryiqhtm' '.claude/skills/dotnet-backend-patterns'Cursor
test -f '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && test -s '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/dotnet-backend-patterns' && cp -R '.skill-downloads/net-backend-development-patterns-mryiqhtm' '.cursor/skills/dotnet-backend-patterns'Codex
test -f '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && test -s '.skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/dotnet-backend-patterns' && cp -R '.skill-downloads/net-backend-development-patterns-mryiqhtm' '.agents/skills/dotnet-backend-patterns'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/net-backend-development-patterns-mryiqhtm'openskills read 'net-backend-development-patterns-mryiqhtm'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/net-backend-development-patterns-mryiqhtm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.