dev-dotnet-backend-engineer

Extends software engineer skill with .NET/C# backend specialization for ASP.NET Core endpoints, EF Core, and CQRS patterns.

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill dev-dotnet-backend-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-dotnet-backend-engineer
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/dev-dotnet-backend-engineer
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill dev-dotnet-backend-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extend the base software engineer skill with a .NET/C# backend specialization to standardize architecture and production-ready practices.

Core Features & Use Cases

  • Domain- and workflow alignment: restricts tasks to .NET backend concerns (ASP.NET Core endpoints, handlers, services, DI, MediatR, migrations) within a clean-architecture and CQRS-driven pattern.
  • Delta-driven customization: merges or overrides base instructions from the parent skill to tailor backend-specific guidance and validation steps.
  • Production-readiness guidance: enforces testing, observability, security checks, and dependency auditing for backend deployments.

Quick Start

Load the base dev-software-engineer skill and apply the .NET backend overrides to tailor the workflow for ASP.NET Core projects.

Frequently Asked Questions about dev-dotnet-backend-engineer

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

FAQPage Schema
How do I enforce clean architecture and CQRS patterns in a .NET backend?

Clean architecture and CQRS in a .NET backend are enforced by applying predefined instruction deltas that standardize ASP.NET Core endpoints, MediatR handlers, and domain services into production-ready workflows.

What is the best way to structure ASP.NET Core projects for production readiness?

Production-ready ASP.NET Core projects require enforcing dependency injection, EF Core migrations, automated testing, and observability patterns. This ensures standardized architecture, security checks, and dependency auditing across backend deployments.

Does this backend specialization work with EF Core and MediatR?

Yes, the .NET backend specialization works specifically with EF Core for data access and MediatR for CQRS command and query separation, tailoring behavior through predefined deltas for these exact libraries.

How do I set up the .NET backend engineer specialization?

To set up the .NET backend specialization, load the base software engineer skill first, then apply the .NET backend overrides to merge and tailor the workflow for ASP.NET Core projects.

Can I use this skill for non-.NET backend frameworks like Node.js or Python?

No, this specialization restricts tasks strictly to .NET backend concerns using C#. It enforces clean architecture, dependency injection, and MediatR workflows specifically tailored for ASP.NET Core environments.

Why use delta-driven customization for .NET backend architecture?

Delta-driven customization merges or overrides base software engineering instructions to tailor backend-specific guidance. This enforces consistent CQRS, MediatR, and clean architecture patterns without rewriting core workflows.