What problem does it solve? .NET teams often struggle to enforce consistent naming, layout, and documentation style conventions beyond what the built-in SDK analyzers provide, and misconfiguring StyleCop leads to rule conflicts and duplicated severity settings. ## Core Features & Use Cases - Package Setup and Detection: Detects existing StyleCop.Analyzers references in .csproj files and bootstraps the package when missing. - Configuration Ownership Split: Keeps rule severity in the root .editorconfig while reserving stylecop.json for StyleCop-specific behavioral settings like documentation, ordering, and layout rules. - Conflict Avoidance: Identifies overlaps with SDK analyzers and other analyzer packs such as Roslynator, and defines clear rule ownership. - Use Case: A team adopting StyleCop.Analyzers in an existing solution uses this Skill to add the package, configure SA rule severities in .editorconfig, and create a schema-backed stylecop.json without duplicating SDK analyzer rules. ## Quick Start Ask the agent to add StyleCop.Analyzers to this solution and configure its rules without losing .editorconfig ownership.
