[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NSPNAEZNMPFC376BYATRHT":3,"skill-same:01M6NSPNAEZNMPFC376BYATRHT":52},{"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":18,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6NSPNAEZNMPFC376BYATRHT","dotnet-best-practices",null,"Ensure .NET\u002FC# code meets best practices for the solution\u002Fproject.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-csharp\u002Fgithub\u002Fdotnet-best-practices\u002FSKILL.md",[],[19,20,21,22,23,24,25],"dotnet","best practices","dotnet best practices","code","project","C#","for","2026-11-10 10:12:30",false,"---\nname: dotnet-best-practices\ndescription: 'Ensure .NET\u002FC# code meets best practices for the solution\u002Fproject.'\n---\n\n# .NET\u002FC# Best Practices\n\nYour task is to ensure .NET\u002FC# code in ${selection} meets the best practices specific to this solution\u002Fproject. This includes:\n\n## Documentation & Structure\n\n- Create comprehensive XML documentation comments for all public classes, interfaces, methods, and properties\n- Include parameter descriptions and return value descriptions in XML comments\n- Follow the established namespace structure: {Core|Console|App|Service}.{Feature}\n\n## Design Patterns & Architecture\n\n- Use primary constructor syntax for dependency injection (e.g., `public class MyClass(IDependency dependency)`)\n- Implement the Command Handler pattern with generic base classes (e.g., `CommandHandler\u003CTOptions>`)\n- Use interface segregation with clear naming conventions (prefix interfaces with 'I')\n- Follow the Factory pattern for complex object creation.\n\n## Dependency Injection & Services\n\n- Use constructor dependency injection with null checks via ArgumentNullException\n- Register services with appropriate lifetimes (Singleton, Scoped, Transient)\n- Use Microsoft.Extensions.DependencyInjection patterns\n- Implement service interfaces for testability\n\n## Resource Management & Localization\n\n- Use ResourceManager for localized messages and error strings\n- Separate LogMessages and ErrorMessages resource files\n- Access resources via `_resourceManager.GetString(\"MessageKey\")`\n\n## Async\u002FAwait Patterns\n\n- Use async\u002Fawait for all I\u002FO operations and long-running tasks\n- Return Task or Task\u003CT> from async methods\n- Use ConfigureAwait(false) where appropriate\n- Handle async exceptions properly\n\n## Testing Standards\n\n- Use MSTest framework with FluentAssertions for assertions\n- Follow AAA pattern (Arrange, Act, Assert)\n- Use Moq for mocking dependencies\n- Test both success and failure scenarios\n- Include null parameter validation tests\n\n## Configuration & Settings\n\n- Use strongly-typed configuration classes with data annotations\n- Implement validation attributes (Required, NotEmptyOrWhitespace)\n- Use IConfiguration binding for settings\n- Support appsettings.json configuration files\n\n## Semantic Kernel & AI Integration\n\n- Use Microsoft.SemanticKernel for AI operations\n- Implement proper kernel configuration and service registration\n- Handle AI model settings (ChatCompletion, Embedding, etc.)\n- Use structured output patterns for reliable AI responses\n\n## Error Handling & Logging\n\n- Use structured logging with Microsoft.Extensions.Logging\n- Include scoped logging with meaningful context\n- Throw specific exceptions with descriptive messages\n- Use try-catch blocks for expected failure scenarios\n\n## Performance & Security\n\n- Use C# 12+ features and .NET 8 optimizations where applicable\n- Implement proper input validation and sanitization\n- Use parameterized queries for database operations\n- Follow secure coding practices for AI\u002FML operations\n\n## Code Quality\n\n- Ensure SOLID principles compliance\n- Avoid code duplication through base classes and utilities\n- Use meaningful names that reflect domain concepts\n- Keep methods focused and cohesive\n- Implement proper disposal patterns for resources\n","# .NET\u002FC# Best Practices\n\nYour task is to ensure .NET\u002FC# code in ${selection} meets the best practices specific to this solution\u002Fproject. This includes:\n\n## Documentation & Structure\n\n- Create comprehensive XML documentation comments for all public classes, interfaces, methods, and properties\n- Include parameter descriptions and return value descriptions in XML comments\n- Follow the established namespace structure: {Core|Console|App|Service}.{Feature}\n\n## Design Patterns & Architecture\n\n- Use primary constructor syntax for dependency injection (e.g., `public class MyClass(IDependency dependency)`)\n- Implement the Command Handler pattern with generic base classes (e.g., `CommandHandler\u003CTOptions>`)\n- Use interface segregation with clear naming conventions (prefix interfaces with 'I')\n- Follow the Factory pattern for complex object creation.\n\n## Dependency Injection & Services\n\n- Use constructor dependency injection with null checks via ArgumentNullException\n- Register services with appropriate lifetimes (Singleton, Scoped, Transient)\n- Use Microsoft.Extensions.DependencyInjection patterns\n- Implement service interfaces for testability\n\n## Resource Management & Localization\n\n- Use ResourceManager for localized messages and error strings\n- Separate LogMessages and ErrorMessages resource files\n- Access resources via `_resourceManager.GetString(\"MessageKey\")`\n\n## Async\u002FAwait Patterns\n\n- Use async\u002Fawait for all I\u002FO operations and long-running tasks\n- Return Task or Task\u003CT> from async methods\n- Use ConfigureAwait(false) where appropriate\n- Handle async exceptions properly\n\n## Testing Standards\n\n- Use MSTest framework with FluentAssertions for assertions\n- Follow AAA pattern (Arrange, Act, Assert)\n- Use Moq for mocking dependencies\n- Test both success and failure scenarios\n- Include null parameter validation tests\n\n## Configuration & Settings\n\n- Use strongly-typed configuration classes with data annotations\n- Implement validation attributes (Required, NotEmptyOrWhitespace)\n- Use IConfiguration binding for settings\n- Support appsettings.json configuration files\n\n## Semantic Kernel & AI Integration\n\n- Use Microsoft.SemanticKernel for AI operations\n- Implement proper kernel configuration and service registration\n- Handle AI model settings (ChatCompletion, Embedding, etc.)\n- Use structured output patterns for reliable AI responses\n\n## Error Handling & Logging\n\n- Use structured logging with Microsoft.Extensions.Logging\n- Include scoped logging with meaningful context\n- Throw specific exceptions with descriptive messages\n- Use try-catch blocks for expected failure scenarios\n\n## Performance & Security\n\n- Use C# 12+ features and .NET 8 optimizations where applicable\n- Implement proper input validation and sanitization\n- Use parameterized queries for database operations\n- Follow secure coding practices for AI\u002FML operations\n\n## Code Quality\n\n- Ensure SOLID principles compliance\n- Avoid code duplication through base classes and utilities\n- Use meaningful names that reflect domain concepts\n- Keep methods focused and cohesive\n- Implement proper disposal patterns for resources\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","code-csharp\u002Fgithub\u002Fdotnet-best-practices",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill dotnet-best-practices",{"tool":44,"command":45},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill dotnet-best-practices",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill dotnet-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fcode-csharp\u002Fgithub\u002Fdotnet-best-practices\u002FSKILL.md",true,[],[53,89,102,122,143,169],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":69,"publishedAt":26},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[59,64],{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[70,71,72,73,25,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"writing clearly and concisely","writing","concisely","text","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":26},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[96,97,71,98,99,80,23,100,101],"crafting effective readmes","README","templates","type","guidance","files",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":111,"publishedAt":26},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000038","人力资源",[112,113,114,115,116,117,118,119,120,121,87],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":26},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[97,129,130,131,116,132,133,23,134,135,31,136,137,138,139,140,87,141,142],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":26},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[150,151,80,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,168],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":26},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[175,176],{"categoryNo":60,"categoryName":61,"taxonomyType":62,"taxonomyTypeDesc":63},{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[178,179,162,139,71,180,77,181,182,183,184,185,186,187,188,84,189,190,88,191],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]