HighFile-scopeJavaScript / TypeScript Plug & play

Prefer specific types over any/unknown where inferable

Replace any/unknown with inferred generics, unions, or precise interfaces when the shape is known.

Why this matters

Preserves type safety and enables better tooling.

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

Avoid

function parse(x: any): any { return JSON.parse(x); }

Prefer

type User={id:string;name:string}; function parseUser(json:string):User{ return JSON.parse(json) as User; }

Bad

let v: any

Good

function id<T>(x:T):T { return x }

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