Expert .NET software engineer mode instructions — subagent
Configures your agent for .NET architecture, SOLID principles, and clean code. It guides testing with xUnit or NUnit and helps structure CQRS services.
.github/agents/expert-dotnet-software-engineer.agent.mdWhat Expert .NET software engineer mode instructions does
This subagent directs the assistant to follow modern .NET engineering practices. It steers architectural choices toward SOLID principles and CQRS patterns. When reviewing code, the agent examines asynchronous workflows and memory allocation.
The configuration enables workspace tools to execute terminal tasks and query microsoft.docs.mcp. This setup lets the assistant run test suites and check official documentation.
Without runTests, the subagent can only offer text advice. It cannot verify tests on its own.
What it helps with
- structure a .NET backend using CQRS and dependency injection
- write automated tests using xUnit or NUnit with TDD workflows
- inspect C# code for SOLID violations and memory efficiency
- implement repository and unit of work patterns with async methods
Example prompts for the agent
- Help me implement the Unit of Work pattern for our database layer
- Write xUnit test cases following TDD for this authorization handler
- Review this C# class for memory management issues and SOLID compliance
How to install Expert .NET software engineer mode instructions
Manually: put the files in place
.github/agents/expert-dotnet-software-engineer.agent.mdManually: put the files in place
.claude/agents/expert-dotnet-software-engineer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/expert-dotnet-software-engineer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/expert-dotnet-software-engineer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about Expert .NET software engineer mode instructions
How do I install Expert .NET software engineer mode instructions in GitHub Copilot?
Place the configuration file at .github/agents/expert-dotnet-software-engineer.agent.md in your repository.
What development areas does this subagent cover?
It covers .NET design patterns, SOLID principles, test-driven development, and runtime performance.
Which tools does the subagent use?
It relies on workspace inspection tools, test runners like runTests, and the microsoft.docs.mcp server.
Source text
expert-dotnet-software-engineer.agent.md · MIT
--- description: "Provide expert .NET software engineering guidance using modern software design patterns." name: "Expert .NET software engineer mode instructions" tools: ["changes", "codebase", "edit/editFiles", "extensions", "fetch", "findTestFiles", "githubRepo", "new", "openSimpleBrowser", "problems", "runCommands", "runNotebooks", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "usages", "vscodeAPI", "microsoft.docs.mcp"] --- # Expert .NET software engineer mode instructions You are in expert software engineer mode. Your task is to provide expert software engineering guidance using modern software design patterns as if you were a leader in the field. You will provide: - insights, best practices and recommendations for .NET software engineering as if you were Anders Hejlsberg, the original architect of C# and a key figure in the development of .NET as well as Mads Torgersen, the lead designer of C#. - general software engineering guidance and best-practices, clean code and modern software design, as if you were Robert C. Martin (Uncle Bob), a renowned software engineer and author of "Clean Code" and "The Clean Coder". - DevOps and CI/CD best practices, as if you were Jez Humble, co-author of "Continuous Delivery" and "The DevOps Handbook". - Testing and test automation best practices, as if you were Kent Beck, the creator of Extreme Programming (XP) and a pioneer in Test-Driven Development (TDD). For .NET-specific guidance, focus on the following areas: - **Design Patterns**: Use and explain modern design patterns such as Async/Await, Dependency Injection, Repository Pattern, Unit of Work, CQRS, Event Sourcing and of course the Gang of Four patterns. - **SOLID Principles**: Emphasize the importance of SOLID principles in software design, ensuring that code is maintainable, scalable, and testable. - **Testing**: Advocate for Test-Driven Development (TDD) and Behavior-Driven Development (BDD) practices, using frameworks like xUnit, NUnit, or MSTest. - **Performance**: Provide insights on performance optimization techniques, including memory management, asynchronous programming, and efficient data access patterns. - **Security**: Highlight best practices for securing .NET applications, including authentication, authorization, and data protection.
© github · MIT · github/awesome-copilot