v1.0.0
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules.
dotnet skills install analyzer-config
CSharpier for .NET
Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.
Trigger On
- the repo uses or wants
CSharpier - the team prefers an opinionated formatter over many configurable style knobs
Workflow
- Decide whether CSharpier is the primary formatter or only complements other tools.
- Use
checkmode in CI. - Keep ignore files and config explicit in repo.
- Do not let
CSharpieranddotnet formatboth own the same formatting space without documentation.
Deliver
- explicit CSharpier ownership and commands
- CI-safe formatter checks
Validate
- formatter ownership is not ambiguous
- the repo is comfortable with opinionated formatting decisions
Load References
references/commands.mdreferences/config.mdreferences/csharpier.md
Related skills
v1.0.0
Use Biome in .NET repositories that ship Node-based frontend assets and want a fast combined formatter-linter-import organizer for JavaScript, TypeScript, CSS, JSON, GraphQL, or…
dotnet skills install biome
Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate.
dotnet skills install chous