Every Mesrai rule, in one place

Elements with multiple attributes should span multiple lines, with one attribute per line.

Ensure that multiple variables are not declared in a single statement. This practice reduces readability and can introduce subtle bugs. Recommend declaring variables separately.

Prefer a single pass when possible (e.g., reduce) over multiple filter/map chains on the same array.

Instantiate expensive clients (DB/HTTP/SDK) once and inject/reuse them; avoid per-call construction.

Use executemany/bulk operations and commit in sensible batches for large writes.

Copy and install dependencies before application sources; ensure .dockerignore excludes node_modules and build outputs.

Exit loops as soon as the goal is achieved using break/return or use any/find/count short-circuiting operations.

Combine filters/maps to minimize passes; avoid creating intermediate collections unnecessarily.

Use appropriate column types/lengths (e.g., NVARCHAR(128) vs NVARCHAR(MAX)) for fields with known bounds.

Component names should start with the highest-level (often most general) words and end with descriptive modifying words.

Check if class members are grouped by accessibility (`public`, `protected`, `private`) to improve code readability and maintainability.

Ensure that the `read(byte[], int, int)` method is overridden in `InputStream` subclasses to improve efficiency.

Prefer data providers for parameterized cases and use assertSame/assertNotSame for type-strict checks; avoid loose equals.

Pin cryptography libraries to vetted versions (e.g., BouncyCastle FIPS) and generate a CycloneDX SBOM as part of the build. Reject PRs introducing floating or insecure versions. (PCI DSS 4.0 Req. 6 & supply chain)

Use a fully qualified Node.js tag including major.minor.patch, not floating majors/minors.

Ensure that multiple statements are not written on the same line. Each statement should be placed on a new line to improve readability.

Use `const` for all references by default within Vue components (e.g., imports, non-reassigned variables, refs obtained via `ref()`). Use `let` only when reassignment of the variable itself is necessary (rare for state). Avoid `var` entirely.

Ensure that non-boolean properties or variables are titled with noun phrases (e.g., `userDetails`, not `getUserDetails`). This improves readability.

Use arrow functions (`=>`) for anonymous functions like callbacks (e.g., in lifecycle hooks, watchers, event handlers, array methods) instead of the `function` keyword, especially when needing lexical `this`.

Detect string formatting using `.format()` or `%`. These methods are less readable and slower than f-strings. Recommend converting string formatting to f-strings for better readability and performance.

Check if type aliases are used instead of interfaces. Interfaces provide better extensibility and readability when defining object shapes.

Ensure that titled classes are used instead of untitled tuples for complex data structures. Tuples should only be used when their purpose is immediately clear.

Use <Link> from 'next/link' for internal routes; reserve <a> only for external URLs or downloadable assets.

Avoid fixed pixel heights for containers; prefer min/max constraints or flexible layouts.