localize

Adapts product experiences across cultures, languages, and markets beyond translation.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill localize-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localize
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/localize
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill localize-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Launching a product in a new market fails when teams treat localization as simple translation. This Skill addresses the deeper problem: cultural assumptions baked into layouts, navigation, colors, icons, date formats, payment flows, and compliance requirements that break or offend when a product crosses borders. ## Core Features & Use Cases - Cultural Dimension Analysis: Applies frameworks like high/low-context communication, power distance, and individualism to generate testable design hypotheses per market. - RTL and i18n Design Guidance: Covers what flips and what doesn't in right-to-left layouts, bidirectional text handling, text expansion (German +30%, Finnish +40%), pluralization rules, and locale-aware date, number, currency, address, and name formats. - Compliance and Testing: Flags market-specific legal requirements (GDPR, PIPL, CCPA, accessibility laws) and provides localization testing methods including pseudo-localization, linguistic QA, and crowd testing. - Use Case: Your team plans to launch in Japan and Saudi Arabia. Use this Skill to produce a cultural adaptation brief, an RTL readiness checklist, and a per-market compliance matrix before writing a single translated string. ## Quick Start Ask the AI to audit your checkout flow for localization readiness before launching in Germany and Japan.

Frequently Asked Questions about localize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a product design for international expansion?

Start with an i18n readiness audit: externalize all strings, make layouts flexible for text expansion, use locale-aware formatting for dates and numbers, and plan RTL support. Then run cultural dimension analysis per target market and validate hypotheses with local user research.

What is the difference between translation and localization?

Translation converts words between languages; localization adapts the entire experience. Localization covers information density, navigation patterns, color meaning, icon comprehension, date formats, trust signals, payment flows, and cultural assumptions about decision-making.

How do I design for RTL languages like Arabic and Hebrew?

Use CSS logical properties like inline-start and inline-end instead of left and right, set dir="rtl" on the root element, and flip directional icons and navigation. Numbers, media controls, and brand logos do not flip. Test with real RTL users and bidirectional content.

Why does text expansion break layouts in German and Finnish?

German expands roughly 30% and Finnish 40% from English, and compound words can exceed 30 characters. Layouts designed for English truncate or overflow. Test with pseudo-localized strings at 150% length to catch breakage before translation.

What compliance requirements affect UX when launching in new markets?

GDPR requires unambiguous consent and data portability in the EU, PIPL mandates data localization in China, and CCPA requires opt-out links in California. Accessibility laws like the EAA and AODA impose WCAG standards, and payment regulations like PSD2 vary by region.

When should I not rely on cultural dimension frameworks?

Cultural frameworks like power distance or uncertainty avoidance are hypotheses, not rules. Never design for stereotypes; every market has subcultures and individual variation. Always validate framework-based assumptions with research and data from real users in the target market.