LowFile-scopeJavaScript / TypeScript Plug & play

Create shared translation accessors/hooks instead of prop drilling

Avoid prop drilling translation functions/objects; expose shared accessors (e.g., a global translation service or context API).

Why this matters

Reduces coupling across UI layers and makes i18n reusable.

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

Avoid

function A(t){ return B(t) } function B(t){ return C(t) } // passing t through multiple layers

Prefer

// pseudo-code: global accessor
const I18n = { t: (k) => k };
function render(){ const { t } = I18n; return t('hello'); }

Bad

pass t through multiple component levels

Good

use a shared i18n accessor instead of drilling

From the same buckets as this rule.

Low
Internationalize user-facing text with next-intl or next-i18next
Do not hardcode user-visible strings in pages/layouts. Use an i18n library integrated with App Router and load dictionaries on the server.
stack-nextjsstack-react+2
Low
Use localized strings instead of hardcoded text
Read UI strings from a localization source (e.g., AppLocalizations, arb) rather than hardcoding.
internationalization-i18nstack-flutter
Low
Use message keys for error messages
Emit stable message keys (for i18n/observability) and resolve user-facing text via localization layers.
internationalization-i18nobservability-logging