Index of every page on this site: llms.txt
All skills
neha avatar

/i18n-and-localization

@eb9f097
Run it yourself

Review React Native localization for extracted strings, plurals, locale-aware formatting, and RTL layout. Use when adding a locale, implementing RTL, or auditing translation readiness.

Use this Skill: https://skilld.dev/gh/neha/rn-developer-skills/i18n-and-localization

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈876 when used: this file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈208 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

i18n and Localization Skill

Applicability

  • Platforms: iOS and Android
  • React Native: 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)

When to Use

  • Adding a locale or extracting user-facing copy
  • Implementing right-to-left layout
  • Formatting dates, numbers, or currencies
  • Auditing a screen for translation readiness

Severity

  • Merge-blocking: a missing translation renders undefined or the raw key as text.
  • Should-fix: plurals, RTL, and pseudo-locale overflow.

Guidance

Strings

  • User-facing copy comes from the translation catalog, including placeholders, alerts, and accessibility labels
  • Plurals, gender, and context use a message format that selects the right form (ICU-style), not string concatenation
  • The source string is a complete sentence so translators can reorder words
  • A missing key falls back to the default locale and does not render the key or undefined

Incorrect:

<Text>{count} {count === 1 ? 'item' : 'items'} in your ${'bag'}</Text>

Correct:

<Text>{t('cart.summary', { count })}</Text>

Formatting

  • Dates, times, numbers, and currencies use the active locale, not a hardcoded en-US pattern
  • Business deadlines and other business logic use the server timezone, not the device clock. This skill owns that rule. Display formatting uses the locale
  • The locale used for formatting is the app locale, which may differ from the device locale when the user picks a language in-app

Layout

  • Layout uses start/end (or equivalent logical edges), not left/right, so RTL mirrors rows, icons, and chevrons
  • Text containers can grow; labels are not fixed to the English string width
  • Text still fits and remains readable at large dynamic type with the longest supported translation
  • Directional icons (back, next) flip in RTL; icons that depict an object do not

Verification

  • A pseudo-locale (padded, accented strings) is checked for overflow and truncation
  • At least one RTL locale is checked for alignment, icons, and text entry
  • The locale from a link or stored preference is validated against the supported set before it is applied

Anti-Patterns

Anti-Pattern Risk Fix
Concatenating translated fragments Word order breaks in other languages One message with named placeholders
Assuming left-to-right padding and chevrons RTL screens point the wrong way Logical start/end, and flip directional icons
Fixed-width labels sized for English German or Arabic clips or overflows Let text wrap or grow, and test the longest locale
Taking a locale from a URL and applying it raw Unexpected locale or injection into formatters Allow only known locale codes

Pitfalls

  • iOS and Android expose the device locale differently, and a per-app language (iOS) does not match Android's per-app locale API. Read the platform value once and store the app's choice separately.
  • An in-app language switch must update already-mounted screens. Changing a module-level string table without re-rendering leaves the old language on screen.
  • Bidirectional text (an English name inside an Arabic sentence) needs the platform's bidi handling. Do not force the whole paragraph to one direction if it mixes scripts.
  • Pseudo-locale overflow often shows up only inside a row that also has an icon and a badge. Test those rows, not only a full-width text block.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    The skill provides instructional guidance and best practices for React Native localization and internationalization. It includes safety-oriented recommendations for validating external inputs such as locale codes and contains no malicious code or patterns.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at eb9f097. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
version
1.0.1
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "i18n",
  "l10n",
  "rtl"
]

README badge

README badge for neha/rn-developer-skills/i18n-and-localization