[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADGF75K3767QR40V9KPWF5":3,"skill-same:01M6ADGF75K3767QR40V9KPWF5":95},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6ADGF75K3767QR40V9KPWF5","dotnet-design-pattern-review",null,"Review the C#\u002F.NET code for design pattern implementation and suggest improvements.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdotnet-design-pattern-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37],"design","review","dotnet","dotnet design pattern review","pattern","code","implementation","C#","for","2026-11-10 10:12:30",false,"---\nname: dotnet-design-pattern-review\ndescription: 'Review the C#\u002F.NET code for design pattern implementation and suggest improvements.'\n---\n\n# .NET\u002FC# Design Pattern Review\n\nReview the C#\u002F.NET code in ${selection} for design pattern implementation and suggest improvements for the solution\u002Fproject. Do not make any changes to the code, just provide a review.\n\n## Required Design Patterns\n\n- **Command Pattern**: Generic base classes (`CommandHandler\u003CTOptions>`), `ICommandHandler\u003CTOptions>` interface, `CommandHandlerOptions` inheritance, static `SetupCommand(IHost host)` methods\n- **Factory Pattern**: Complex object creation service provider integration\n- **Dependency Injection**: Primary constructor syntax, `ArgumentNullException` null checks, interface abstractions, proper service lifetimes\n- **Repository Pattern**: Async data access interfaces provider abstractions for connections\n- **Provider Pattern**: External service abstractions (database, AI), clear contracts, configuration handling\n- **Resource Pattern**: ResourceManager for localized messages, separate .resx files (LogMessages, ErrorMessages)\n\n## Review Checklist\n\n- **Design Patterns**: Identify patterns used. Are Command Handler, Factory, Provider, and Repository patterns correctly implemented? Missing beneficial patterns?\n- **Architecture**: Follow namespace conventions (`{Core|Console|App|Service}.{Feature}`)? Proper separation between Core\u002FConsole projects? Modular and readable?\n- **.NET Best Practices**: Primary constructors, async\u002Fawait with Task returns, ResourceManager usage, structured logging, strongly-typed configuration?\n- **GoF Patterns**: Command, Factory, Template Method, Strategy patterns correctly implemented?\n- **SOLID Principles**: Single Responsibility, Open\u002FClosed, Liskov Substitution, Interface Segregation, Dependency Inversion violations?\n- **Performance**: Proper async\u002Fawait, resource disposal, ConfigureAwait(false), parallel processing opportunities?\n- **Maintainability**: Clear separation of concerns, consistent error handling, proper configuration usage?\n- **Testability**: Dependencies abstracted via interfaces, mockable components, async testability, AAA pattern compatibility?\n- **Security**: Input validation, secure credential handling, parameterized queries, safe exception handling?\n- **Documentation**: XML docs for public APIs, parameter\u002Freturn descriptions, resource file organization?\n- **Code Clarity**: Meaningful names reflecting domain concepts, clear intent through patterns, self-explanatory structure?\n- **Clean Code**: Consistent style, appropriate method\u002Fclass size, minimal complexity, eliminated duplication?\n\n## Improvement Focus Areas\n\n- **Command Handlers**: Validation in base class, consistent error handling, proper resource management\n- **Factories**: Dependency configuration, service provider integration, disposal patterns\n- **Providers**: Connection management, async patterns, exception handling and logging\n- **Configuration**: Data annotations, validation attributes, secure sensitive value handling\n- **AI\u002FML Integration**: Semantic Kernel patterns, structured output handling, model configuration\n\nProvide specific, actionable recommendations for improvements aligned with the project's architecture and .NET best practices.\n","# .NET\u002FC# Design Pattern Review\n\nReview the C#\u002F.NET code in ${selection} for design pattern implementation and suggest improvements for the solution\u002Fproject. Do not make any changes to the code, just provide a review.\n\n## Required Design Patterns\n\n- **Command Pattern**: Generic base classes (`CommandHandler\u003CTOptions>`), `ICommandHandler\u003CTOptions>` interface, `CommandHandlerOptions` inheritance, static `SetupCommand(IHost host)` methods\n- **Factory Pattern**: Complex object creation service provider integration\n- **Dependency Injection**: Primary constructor syntax, `ArgumentNullException` null checks, interface abstractions, proper service lifetimes\n- **Repository Pattern**: Async data access interfaces provider abstractions for connections\n- **Provider Pattern**: External service abstractions (database, AI), clear contracts, configuration handling\n- **Resource Pattern**: ResourceManager for localized messages, separate .resx files (LogMessages, ErrorMessages)\n\n## Review Checklist\n\n- **Design Patterns**: Identify patterns used. Are Command Handler, Factory, Provider, and Repository patterns correctly implemented? Missing beneficial patterns?\n- **Architecture**: Follow namespace conventions (`{Core|Console|App|Service}.{Feature}`)? Proper separation between Core\u002FConsole projects? Modular and readable?\n- **.NET Best Practices**: Primary constructors, async\u002Fawait with Task returns, ResourceManager usage, structured logging, strongly-typed configuration?\n- **GoF Patterns**: Command, Factory, Template Method, Strategy patterns correctly implemented?\n- **SOLID Principles**: Single Responsibility, Open\u002FClosed, Liskov Substitution, Interface Segregation, Dependency Inversion violations?\n- **Performance**: Proper async\u002Fawait, resource disposal, ConfigureAwait(false), parallel processing opportunities?\n- **Maintainability**: Clear separation of concerns, consistent error handling, proper configuration usage?\n- **Testability**: Dependencies abstracted via interfaces, mockable components, async testability, AAA pattern compatibility?\n- **Security**: Input validation, secure credential handling, parameterized queries, safe exception handling?\n- **Documentation**: XML docs for public APIs, parameter\u002Freturn descriptions, resource file organization?\n- **Code Clarity**: Meaningful names reflecting domain concepts, clear intent through patterns, self-explanatory structure?\n- **Clean Code**: Consistent style, appropriate method\u002Fclass size, minimal complexity, eliminated duplication?\n\n## Improvement Focus Areas\n\n- **Command Handlers**: Validation in base class, consistent error handling, proper resource management\n- **Factories**: Dependency configuration, service provider integration, disposal patterns\n- **Providers**: Connection management, async patterns, exception handling and logging\n- **Configuration**: Data annotations, validation attributes, secure sensitive value handling\n- **AI\u002FML Integration**: Semantic Kernel patterns, structured output handling, model configuration\n\nProvide specific, actionable recommendations for improvements aligned with the project's architecture and .NET best practices.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fdotnet-design-pattern-review",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add github\u002Fawesome-copilot --skill dotnet-design-pattern-review",{"tool":59,"command":60},"bunx","bunx skills add github\u002Fawesome-copilot --skill dotnet-design-pattern-review",{"tool":62,"command":63},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill dotnet-design-pattern-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fdotnet-design-pattern-review\u002FSKILL.md",true,[67,73,77,81,87,91],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcryptography_implementation.md","REFERENCE","参考文档",1622,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Freferences\u002Fcryptography_implementation.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fpenetration_testing_guide.md",1620,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Freferences\u002Fpenetration_testing_guide.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fsecurity_architecture_patterns.md",1625,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Freferences\u002Fsecurity_architecture_patterns.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fpentest_automator.py","SCRIPT","脚本",3135,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Fscripts\u002Fpentest_automator.py",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fsecurity_auditor.py",3130,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Fscripts\u002Fsecurity_auditor.py",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fthreat_modeler.py",3120,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Fsenior-security\u002Fscripts\u002Fthreat_modeler.py",[96,128,155,182,216,233],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":108,"publishedAt":38},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[102,105],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,110,111,112,113,114,30,115,116,117,118,119,120,121,122,123,124,125,126,127],"supabase","rls","supabase rls","supabase rls policies","project","when","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":38},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[134],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,138,139,140,141,37,142,143,144,145,146,147,148,149,150,151,152,153,154],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":165,"publishedAt":38},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[166,34,167,168,169,170,37,113,171,172,173,174,175,176,177,124,178,179,180,181],"custom","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":186,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":38},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":163,"categoryName":164,"taxonomyType":26,"taxonomyTypeDesc":27},[194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,114,209,210,211,212,213,37,214,215],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":220,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":229,"publishedAt":38},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[224,225,228],{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[230,139,203,231,232],"resemble detect","https","identity",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":220,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":244,"publishedAt":38},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[240,243],{"categoryNo":241,"categoryName":242,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,248,34,30,9,138,249,250,231,251,252,253,254,255,256,257,258,259,260,261,122,262,263,264,265],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]