Every Mesrai rule, in one place

Do not use the error‐suppression operator '@' before function calls or expressions. Instead, handle potential errors properly using return checks or exceptions (try/catch).

Identify overly defensive code that checks for unrealistic conditions, such as excessive `nil?` checks or redundant type verifications.

Don't place a defer inside a loop that iterates many times (especially if the loop is performance-critical). Defer calls won't run until the function returns and each call has a small overhead; instead, perform the operation directly in the loop when possible.

Check for the use of getters and setters. These can introduce unexpected side effects and have limited compiler support. Recommend using regular methods unless required by a framework.

Detect unnecessary semicolons at the end of statements. Ruby does not require semicolons, so they should be removed unless multiple statements exist on the same line.

Detect occurrences of the comma operator in expressions. The comma operator can make code harder to read and debug, as it executes multiple expressions but only returns the value of the last one.

Ensure that CORS policies are properly defined. Weak or missing CORS policies may allow unauthorized domains to access your resources, leading to security vulnerabilities.

Ensure that imports are explicitly listed and avoid using wildcard imports (`import package.*;`).

Implement a scheduled worker to delete or anonymize records past expires_at, with metrics on deletions and failures. Dry-run mode allowed only in non-prod.

Base components (a.k.a. presentational, dumb, or pure components) that apply app-specific styling and conventions should all begin with a specific prefix, such as `Base`, `App`, or `V`.

In Kotlin Ktor, install CachingHeaders and Compression. Set immutable caching for hashed resources and no-cache for HTML; include "Vary: Accept-Encoding".

Apply memoization (functools.lru_cache) or explicit caches for pure, expensive computations keyed by inputs.

Cache frequently used, rarely changing query results in memory or an external cache with appropriate TTL/invalidations.

Do not recompute expensive values inside loops; compute once and reuse.

Hoist and reuse costly objects (Pattern, DateTimeFormatter) rather than re-creating per use.

Memoize expensive results (regex, serializers, tokens) and refresh on expiry using a thread-safe cache.

Hoist constant work out of loops and memoize expensive computations when inputs repeat.

Use `catch (e, stack)` and log both exception and stack; do not log message-only.

Use Directory.Packages.props at the repo root to declare PackageVersion entries. Workspace .csproj files must reference packages without embedding Version attributes.

Route all analytics events through a single service/helper instead of calling the SDK directly from widgets and blocs.

Define configuration values in one place (env/config file/const class) and reference them; avoid scattering magic strings.

Generate cache/Redis keys through a single utility with clear namespaces and versioning.

In the root Cargo.toml, define [workspace] members and manage shared versions under [workspace.dependencies]. Member Cargo.toml files must not pin versions for crates declared centrally.

Define shared string literals (route names, keys, claim types) as constants/enums in a single place.