LowFile-scopeC# Plug & play

Use proper naming conventions

Follow .NET naming: PascalCase for types/methods/properties, camelCase for locals/parameters, and meaningful names.

Why this matters

Consistency improves readability and tooling support.

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

Avoid

public int calc_val(int X) { return X; }

Prefer

public int CalculateValue(int x) { return x; }

Bad

public string get_name()

Good

public string GetName()

From the same buckets as this rule.

Critical
Avoid Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Prefer `str.replace()` Over `re.sub()` for Simple Cases
Detect uses of `re.sub()` where regular expressions are not needed. For simple string replacements, `str.replace()` is more efficient and should be used instead.
performance-efficiencystack-python+1
Critical
Use Factory Method Injection in `@Configuration` Classes
Ensure that factory method injection is used in `@Configuration` classes instead of `@Autowired` field injection.
module-architecturestyle-conventions