LowFile-scopeC# Plug & play

Fix file-to-class name mismatches

Keep public types in files with matching names (one top-level type per file) to improve navigation.

Why this matters

Aids discoverability and reduces confusion for tooling and readers.

Side-by-side examples engineers can pattern-match during review.

Avoid

// File: Utils.cs
public class Helper { }

Prefer

// File: Helper.cs
public class Helper { }

Bad

File Foo.cs contains class Bar

Good

File Bar.cs contains class Bar

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening