dotnet-best-practices

Enforce .NET/C# best practices across a solution.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill dotnet-best-practices-bingeli1379
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-best-practices
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eureka-sdd/skills/dotnet-best-practices
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill dotnet-best-practices-bingeli1379

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures .NET/C# code in your solution adheres to established best practices, reducing defects and maintenance costs.

Core Features & Use Cases

  • XML documentation and descriptive comments for public API members.
  • Consistent namespace conventions and design patterns (DI, command handler, factory).
  • Strong testing, configuration, and resource handling standards for robust apps.

Quick Start

Apply the dotnet-best-practices guidelines to the target solution to enforce C# best practices.

Frequently Asked Questions about dotnet-best-practices

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

FAQPage Schema
How do I enforce C# best practices across a dotnet solution?

Apply dotnet-best-practices guidelines to validate XML documentation, naming conventions, dependency injection, async/await, and resource management configurations across your dotnet projects to ensure structured code quality.

What dotnet architecture patterns and standards should my solution follow?

Your dotnet solution should follow consistent namespace conventions, dependency injection, command handler, and factory patterns, alongside strong testing, configuration, and error handling standards for robust applications.

Can I use this to check XML documentation and public API comments in C#?

Yes, you can validate XML documentation and descriptive comments for public API members in C# to ensure your codebase satisfies deterministic development guidelines and maintainability requirements.

Does this cover async/await and resource management testing standards?

Yes, it covers async/await and resource management testing standards, ensuring robust application handling by validating these specific configurations and patterns across your dotnet projects.

What is the best way to validate dependency injection configurations in dotnet?

The best way to validate dependency injection configurations is to enforce consistent design patterns and naming conventions across the solution, reducing defects and maintenance costs.