Every Mesrai rule, in one place

Use strict comparison operators (=== and !==) instead of loose (== and !=) in most cases. Strict comparisons check both type and value, avoiding PHP’s implicit type coercion pitfalls.

Avoid re-creating existing UI components or duplicating styles (CSS/Tailwind) when the company design system already provides an official component. If the PR touches UI and a design system entry point is referenced (e.g., `ui/index.ts`, `design-system.md`), use it as the source of truth and suggest the equivalent official component.

Check for functions with unused parameters and ensure they are titled with `_` or `__` to indicate they are intentionally unused.

Prop names should always use camelCase during declaration. When used inside in-DOM templates, props should be kebab-cased. Single-File Components templates and JSX can use either kebab-case or camelCase props. Casing should be consistent.

Use context.WithTimeout for HTTP and DB calls; log request deadlines and results; treat timeouts as audit-worthy events.

Ensure that event listeners are removed when no longer needed. Not doing so can lead to memory leaks and unnecessary resource consumption.

For async routes, add loading.tsx for suspense fallbacks and error.tsx for boundaries. Use notFound() for 404 states.

Check for hash key lookups without default values. If a missing key is accessed, suggest using `fetch` with a default value.

Non-empty HTML attribute values should always be inside quotes (single or double, whichever is not used in JS).

Ensure that isMounted is not used in React components. This method is deprecated and can cause unreliable state updates. Suggest using cleanup functions or useRef instead.

Add an 'Alternatives' section listing at least two plausible options with pros/cons and reasons for rejection.

Wrap logger to filter emails and tokens using regex before logging; include trace_id in every entry.

Replace repeated similar if/elif blocks with data-driven loops or dispatch tables.

Centralize repeated dialog creation/action handlers into a helper to ensure consistent UX and error handling.

Create factories/builders for repeated dialog/modal construction with configurable parameters.

Centralize repeated validation rules into helpers or small packages. Reuse them across handlers, services, and jobs.

Split long methods into cohesive private helpers with clear names and single responsibilities.

Break deep map/flatMap chains into named suspend functions or use runCatching/Result for clearer composition.

Where relevant, include links to RFCs, regulatory guidance, or benchmarks in the ADR (e.g., RFC 9110 for HTTP, PCI DSS sections), under a 'References' section.

After using external resources (DB connections, open files, sockets), release them properly. Use fclose(), close database connections or finally blocks to ensure cleanup even if errors occur.

Do not include commented-out code, unused files, or unrelated snapshots. Keep diffs minimal and relevant to the change.

Delete unreachable branches and unused methods; rely on VCS for history.

Delete Console.WriteLine, Debug.WriteLine, and temporary diagnostics before merging; rely on structured logging.

Do not define the same method multiple times; consolidate behavior in one place.