LowFile-scopeRuby Plug & play

Use Rails conventions for resource naming

Follow Rails conventions (plural resource routes, model singular class names, snake_case files).

Why this matters

Reduces surprise and tooling friction.

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

Avoid

resources :user
class Users < ApplicationRecord; end

Prefer

resources :users
class User < ApplicationRecord; end

Bad

get '/User/index'

Good

resources :users

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