Agent skill · software engineering · github
dotnet-design-pattern-review
Review the C#/.NET code for design pattern implementation and suggest improvements.
Why this skill is useful
Provides a detailed review framework for assessing design pattern implementations in C#/.NET, which includes specific patterns and best practices not commonly known to AI.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
.NET/C# Design Pattern Review Review the C#/.NET code in ${selection} for design pattern implementation and suggest improvements for the solution/project. Do not make any changes to the code, just provide a review. Required Design Patterns Command Pattern: Generic base classes (CommandHandler<TOptions>), ICommandHandler<TOptions> interface, CommandHandlerOptions inheritance, static SetupCommand(IHost host) methods Factory Pattern: Complex object creation service provider integration Dependency Injection: Primary constructor syntax, ArgumentNullException null checks, interface abstractions, proper service lifetimes Repository Pattern: Async data access interfaces provider abstractions for connections Provider Pattern: External service abstractions (database, AI), clear contracts, configuration handling Resource Pattern: ResourceManager for localized messages, separate .resx files (LogMessages, ErrorMessages) Review Checklist Design Patterns: Identify patterns used. Are Command Handler, Factory, Provider, and Repository patterns correctly implemented? Missing beneficial patterns? Architecture: Follow namespace conventions ({Core Console App Service}.{Feature})? Proper separation between Core/Console projects? Modular and readable? .NET Best Practices: Primary constructors, async/await with Task returns, ResourceManager usage, structured logging, strongly-typed configuration? GoF Patterns: Command, Factory, Template Method, Strategy patterns correctly implemented? SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion violations? Performance: Proper async/await, resource disposal, ConfigureAwait(false), parallel processing opportunities? Maintainability: Clear separation of concerns, consistent error handling, proper configuration usage? Testability: Dependencies abstracted via interfaces, mockable components, async testability, AAA pattern compatibility? Security: Input validation, secure credential handl …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/dotnet-design-pattern-review