AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

UX design

Internationalization Readiness Audit

Audit UI copy, layouts, and interactions for i18n issues like truncation, plurals, RTL, and locale formatting.

Prompt

Audit this UI/feature for internationalization (i18n) readiness.

Context:
- Product/feature: [name]
- Platforms: [web / iOS / Android]
- Target locales: [list]
- Target scripts: [Latin/Cyrillic/Arabic/etc.]

Inputs:
[Paste UI copy, screenshots/links, key flows, and any constraints]

Provide:

1. Copy & String Risks
   - String concatenation risks
   - Idioms/slang that won?t translate cleanly
   - Placeholder/variable usage issues (e.g., ordering, punctuation)
   - Plurals, gender, politeness/formality concerns
   - Ambiguity that needs disambiguation for translators

2. Layout & Component Risks
   - Length expansion risks (30?50% expansion)
   - Truncation/wrapping/overflow risks
   - Fixed-width containers and buttons
   - Line breaks, hyphenation, and responsiveness concerns

3. RTL & Directionality
   - Components that must mirror vs must not mirror
   - Icon directionality
   - Alignment, spacing, and reading order issues
   - Motion/animation direction considerations

4. Locale Formatting & Inputs
   - Date/time/number/currency formatting risks
   - Time zone assumptions
   - Address/name/phone input considerations
   - Validation and error messaging considerations

5. Fallback & Missing Translation Behavior
   - Fallback language expectations
   - What happens on missing keys
   - Mixed-language UI risks

6. Prioritized Fix List
   - Severity (P0/P1/P2)
   - Suggested fix (copy change, layout change, component behavior change)
   - Owner (design/content/engineering)

Format as a concise audit report with a prioritized punch list.

How to use

  1. 01

    Replace [name], [web / iOS / Android], [list], and [Latin/Cyrillic/Arabic/etc.] with your specific details

  2. 02

    Gather your UI materials: Collect UI copy, screenshots, key flows, and design constraints

  3. 03

    Replace [Paste UI copy, screenshots/links, key flows, and any constraints] with your materials. If you have screenshots, upload them

  4. 04

    Add context before the prompt: Describe your product and target locales. Example: "Product: E-commerce checkout. Platforms: Web. Target locales: English, Spanish, French, German. Scripts: Latin."

  5. 05

    Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude (preferably with vision if using screenshots)

  6. 06

    Review the audit report: Check copy risks, layout risks, RTL considerations, and locale formatting issues

  7. 07

    Prioritize fixes: Focus on P0 issues first (critical), then P1 (important), then P2 (nice to have)

  8. 08

    Export to tracking tool: Copy the prioritized fix list to Jira, Linear, or your project management tool

Tips

  • Include UI screenshots: Upload actual UI screenshots for visual i18n risk analysis
  • Specify target languages: Mention specific languages (e.g., "German, Spanish, Arabic") so AI can identify language-specific issues
  • For RTL: Mention "Include Arabic and Hebrew" so AI focuses on RTL directionality issues
  • Request specific sections: Ask "Focus on copy risks" or "Focus on layout risks" for targeted audit
  • Combine with length expansion test: Use this audit alongside the length expansion stress test for comprehensive i18n coverage