Source profileQuality 67/100

github/awesome-copilot/skills/dotnet-best-practices/SKILL.md

dotnet-best-practices

Ensure .NET/C# code meets best practices for the solution/project.

Source repository stars
37,126
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Your task is to ensure .NET/C code in ${selection} meets the best practices specific to this solution/project. This includes:

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/dotnet-best-practices"
    Safe inspection promptEditorial

    Inspect the Agent Skill "dotnet-best-practices" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/dotnet-best-practices/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Documentation & Structure

      Create comprehensive XML documentation comments for all public classes, interfaces, methods, and properties

      Create comprehensive XML documentation comments for all public classes, interfaces, methods, and propertiesInclude parameter descriptions and return value descriptions in XML commentsFollow the established namespace structure: {Core|Console|App|Service}.{Feature}
    2. 02

      Design Patterns & Architecture

      Use primary constructor syntax for dependency injection (e.g., public class MyClass(IDependency dependency))

      Use primary constructor syntax for dependency injection (e.g., public class MyClass(IDependency dependency))Implement the Command Handler pattern with generic base classes (e.g., CommandHandler)Use interface segregation with clear naming conventions (prefix interfaces with 'I')
    3. 03

      Dependency Injection & Services

      Use constructor dependency injection with null checks via ArgumentNullException

      Use constructor dependency injection with null checks via ArgumentNullExceptionRegister services with appropriate lifetimes (Singleton, Scoped, Transient)Use Microsoft.Extensions.DependencyInjection patterns
    4. 04

      Resource Management & Localization

      Use ResourceManager for localized messages and error strings

      Use ResourceManager for localized messages and error stringsSeparate LogMessages and ErrorMessages resource filesAccess resources via resourceManager.GetString("MessageKey")

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score67/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/dotnet-best-practices/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    .NET/C# Best Practices

    Your task is to ensure .NET/C# code in ${selection} meets the best practices specific to this solution/project. This includes:

    Documentation & Structure

    • Create comprehensive XML documentation comments for all public classes, interfaces, methods, and properties
    • Include parameter descriptions and return value descriptions in XML comments
    • Follow the established namespace structure: {Core|Console|App|Service}.{Feature}

    Design Patterns & Architecture

    • Use primary constructor syntax for dependency injection (e.g., public class MyClass(IDependency dependency))
    • Implement the Command Handler pattern with generic base classes (e.g., CommandHandler<TOptions>)
    • Use interface segregation with clear naming conventions (prefix interfaces with 'I')
    • Follow the Factory pattern for complex object creation.

    Dependency Injection & Services

    • Use constructor dependency injection with null checks via ArgumentNullException
    • Register services with appropriate lifetimes (Singleton, Scoped, Transient)
    • Use Microsoft.Extensions.DependencyInjection patterns
    • Implement service interfaces for testability

    Resource Management & Localization

    • Use ResourceManager for localized messages and error strings
    • Separate LogMessages and ErrorMessages resource files
    • Access resources via _resourceManager.GetString("MessageKey")

    Async/Await Patterns

    • Use async/await for all I/O operations and long-running tasks
    • Return Task or Task from async methods
    • Use ConfigureAwait(false) where appropriate
    • Handle async exceptions properly

    Testing Standards

    • Use MSTest framework with FluentAssertions for assertions
    • Follow AAA pattern (Arrange, Act, Assert)
    • Use Moq for mocking dependencies
    • Test both success and failure scenarios
    • Include null parameter validation tests

    Configuration & Settings

    • Use strongly-typed configuration classes with data annotations
    • Implement validation attributes (Required, NotEmptyOrWhitespace)
    • Use IConfiguration binding for settings
    • Support appsettings.json configuration files

    Semantic Kernel & AI Integration

    • Use Microsoft.SemanticKernel for AI operations
    • Implement proper kernel configuration and service registration
    • Handle AI model settings (ChatCompletion, Embedding, etc.)
    • Use structured output patterns for reliable AI responses

    Error Handling & Logging

    • Use structured logging with Microsoft.Extensions.Logging
    • Include scoped logging with meaningful context
    • Throw specific exceptions with descriptive messages
    • Use try-catch blocks for expected failure scenarios

    Performance & Security

    • Use C# 12+ features and .NET 8 optimizations where applicable
    • Implement proper input validation and sanitization
    • Use parameterized queries for database operations
    • Follow secure coding practices for AI/ML operations

    Code Quality

    • Ensure SOLID principles compliance
    • Avoid code duplication through base classes and utilities
    • Use meaningful names that reflect domain concepts
    • Keep methods focused and cohesive
    • Implement proper disposal patterns for resources

    Alternatives

    Compare before choosing

    Computed 9438,313

    wshobson/agents

    brand-landingpage

    Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

    Computed 91933

    dpearson2699/swift-ios-skills

    ios-localization

    Implement, review, or improve localization and internationalization in iOS/macOS apps — String Catalogs (.xcstrings), generated localizable symbols, stable key naming, LocalizedStringKey, LocalizedStringResource, pluralization, FormatStyle for numbers/dates/measurements, right-to-left layout, Dynamic Type, and locale-aware formatting. Use when adding multi-language support, setting up String Catalogs, enabling generated symbols for compile-time-safe localization keys, handling plural forms, form

    Computed 9037,126

    github/awesome-copilot

    screen-recording

    Create annotated animated GIF demos and screen recordings for pull requests and documentation. Covers frame capture, timing, imageio-based GIF creation, and per-frame annotation workflows.

    Computed 8537,126

    github/awesome-copilot

    create-technical-spike

    Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.