LowFile-scopeRuby Plug & play

Use translation keys for user-facing text

Do not hardcode UI strings; use I18n keys with proper scopes.

Why this matters

Enables localization and consistent copy.

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

Avoid

flash[:alert] = "Invalid login"

Prefer

flash[:alert] = t("sessions.invalid_login")

Bad

render plain: "Done"

Good

render plain: t('common.done')

From the same buckets as this rule.

Low
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).
internationalization-i18nmodule-architecture
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