Check my design is ready for translation and localization
Reviews screens for text expansion, layout, formats, imagery, and cultural issues before your product launches in new languages and regions.
The prompt
Review my design for localization readiness.
Product and screens: [WHAT TO REVIEW - describe the layouts and paste the copy]
Target languages and regions: [e.g. German, Japanese, Arabic, Brazilian Portuguese]
Platform and design system: [WEB / MOBILE; COMPONENT LIBRARY]
Known constraints: [FIXED-WIDTH BUTTONS, TEXT IN IMAGES, CHARACTER LIMITS]
Check:
- Text expansion: flag elements that will break if text grows 30-40% (more for short strings), such as buttons, tabs, nav, badges, and table headers. Suggest wrapping, truncation rules, or flexible layout.
- Right-to-left (if relevant): mirroring of layout, icons that should and should not flip, number and mixed-direction text.
- Formats: dates, times, numbers, currencies, addresses, names, phone numbers, units, sorting, plural forms.
- Copy: concatenated strings, sentences built from pieces, idioms, puns, and gendered or culturally specific wording that will not translate.
- Text in images or icons, and imagery, colors, gestures, or symbols that carry different meanings in target regions.
- Fonts: character support (e.g. CJK, Arabic) and line height for scripts with tall marks.
- Input: names and addresses that do not fit Western assumptions.
Return a findings table (Screen | Element | Issue | Affected locales | Fix), a list of strings to rewrite for translators with context notes, and the top 5 fixes before handoff to localization.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- WHAT TO REVIEW - describe the layouts and paste the copy
- e.g. German, Japanese, Arabic, Brazilian Portuguese
- WEB / MOBILE; COMPONENT LIBRARY
- FIXED-WIDTH BUTTONS, TEXT IN IMAGES, CHARACTER LIMITS
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Find and remove friction in a signup or checkout flowAudits a conversion flow step by step for friction and doubt, then ranks fixes by expected impact and effort, with test ideas.
- Review a part design for manufacturability before releaseA design for manufacturability (DFM) review that flags features driving cost, scrap, or long lead times, with suggested changes ranked by impact.
- Decide which enterprise features to build before moving upmarketA prioritized enterprise-readiness roadmap covering SSO, SCIM, audit logs, permissions, and admin controls, tied to deals.
- Audit and fix the color palette in my app or websiteReviews how color is used across your interface, then gives a consistent palette, color tokens, contrast fixes, and dark-mode adjustments.