[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASFW8CW5E8F1AC6RSMDWN8":3,"skill-same:01M7ASFW8CW5E8F1AC6RSMDWN8":44},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7ASFW8CW5E8F1AC6RSMDWN8","dotnet-best-practices",null,"Ensure .NET\u002FC# code meets best practices for the solution\u002Fproject.","Rico631\u002Fdotnet-confluence-exporter","Rico631","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42249794?v=4","01M7ASE3XMNRJTS7QZGGKX9VPA","Dmitrii","01M7ASE3YA38Q52FVBGFJKVKT6",0,"MIT","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdotnet-best-practices\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","9a14d60def9ae4b571074a73ce7388ffa229401a",".claude\u002Fskills\u002Fdotnet-best-practices","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter","https:\u002F\u002Fgithub.com\u002FRico631","2026-09-22 14:26:02",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Rico631\u002Fdotnet-confluence-exporter --skill dotnet-best-practices",{"tool":36,"command":37},"bunx","bunx skills add Rico631\u002Fdotnet-confluence-exporter --skill dotnet-best-practices",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Rico631\u002Fdotnet-confluence-exporter --skill dotnet-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdotnet-best-practices\u002FSKILL.md",true,[],[45,53,60,67,74,81],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":49,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7ASMCSQHKHGD394SM9V33ZS","dotnet-confluence-exporter","A brief description of what this skill does","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"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":59,"publishedAt":19},"01M7ASM6JNCWTFA65AFBZVEEQD","openspec-update-change","Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user says \"openspec update change\" or \"opsx update\". If the user means the openspec update CLI command, which refreshes generated files, run that command instead. Never edits code.","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenspec-update-change\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7ASM3S6ZWX16JESTP9DECY5","openspec-sync-specs","Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says \"openspec sync\" or \"opsx sync\".","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenspec-sync-specs\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7ASKZM4RGKS4C3ND4XJST1M","openspec-propose","Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says \"openspec propose\" or \"opsx propose\".","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ASKSZ250EDTZBXHK775225","openspec-explore","Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says \"openspec explore\" or \"opsx explore\".","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenspec-explore\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ASKKWNGSDYHPVRRC5M1M4X","openspec-archive-change","Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says \"openspec archive\" or \"opsx archive\".","https:\u002F\u002Fgithub.com\u002FRico631\u002Fdotnet-confluence-exporter\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fopenspec-archive-change\u002FSKILL.md",[],[]]