Localization Design

CommunityPopular

Owl-Listener

localization-design

Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use `ux-writing` (designer-toolkit).

Overview

Publisher	Owl-Listener
Repository	`designer-skills`
Skill name	`localization-design`
Stars	2.7K
Forks	384
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Localization Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/designer-skills/tree/main/design-systems/skills/localization-design

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p .claude/skills
cp -r /tmp/designer-skills/design-systems/skills/localization-design .claude/skills/localization-design

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Localization Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Localization Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Localization Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Localization Design

You are an expert in designing UI that works across languages, scripts, and cultures without requiring per-locale redesigns.

What You Do

You apply localization-aware design principles to ensure components, layouts, and content can be adapted to any target locale without breaking — and that cultural differences in color, iconography, and conventions are accounted for.

Text Expansion

The most common localization failure. English is compact; most target languages are longer:

Language	Typical expansion vs English
German	+20–35%
French	+15–25%
Finnish	+30–40%
Arabic (translated)	−20–30% (but RTL and different script)
Japanese/Chinese	Often shorter, but very different typographic rules
Design for text expansion:

Never size containers to fit English copy — use flexible heights and widths
Test layouts with German or Finnish translations as worst-case proxies before other locales exist
Truncation with ellipsis is an acceptable last resort, but provide full text via tooltip/expand
Buttons: use min-width, not fixed width; allow wrapping for extreme cases in narrow contexts
Navigation labels: test all nav items together at 130% length to validate menu doesn't break

RTL (Right-to-Left) Support

Arabic, Hebrew, Persian, and Urdu read right-to-left. The entire layout mirrors:

Content flow: text, lists, and reading order reverse
Layout mirroring: sidebars, navigation, and content areas flip; left margin becomes right margin
Icon mirroring: directional icons (arrows, chevrons, back button) mirror; non-directional icons (camera, settings) do not
CSS logical properties: use margin-inline-start instead of margin-left; padding-block-end instead of padding-bottom — these flip automatically with dir="rtl"
Text alignment: use text-align: start not text-align: left
Numbers: numerals remain LTR within RTL text in most contexts; don't mirror number displays What does not mirror in RTL:
Logos and brand marks
Clocks and time displays
Mathematical notation
Images and illustrations (usually — context-dependent)
Video player controls (debated; mirror directional but not play/pause)

Typography for Non-Latin Scripts

Arabic and Hebrew: cursive scripts with letter-joining rules; larger minimum font sizes (16px+) for readability
CJK (Chinese, Japanese, Korean): square characters; different optimal line-height and letter-spacing than Latin; different measure rules
Devanagari (Hindi) and other Indic scripts: complex ligatures; test with font stacks that include proper fallbacks
Never fake-bold or fake-italic non-Latin scripts — use genuine weights from the font family

Cultural Considerations

Color

Color meaning varies significantly by culture:

Color	Western association	Example alternative association
Red	Danger, error	Luck/prosperity (China), mourning (South Africa)
White	Clean, minimal	Mourning (many East Asian cultures)
Green	Success, go	Unfaithfulness (China), danger (some Middle Eastern contexts)

Don't rely on color alone for semantic meaning (this is also an accessibility requirement)
Test color choices with cultural consultants for high-stakes or global products

Iconography

Hand gestures (thumbs up, OK sign) have offensive meanings in some cultures — avoid
Postal and civic icons (mailbox, house, phone) vary by region — use abstract or universally-recognizable forms
Religious and food symbolism is culturally loaded — avoid unless necessary and tested

Date, Time, and Number Formats

Date formats vary: MM/DD/YYYY (US), DD/MM/YYYY (UK/EU), YYYY-MM-DD (ISO)
Use locale-aware formatting via Intl.DateTimeFormat / equivalent
Currency: symbol position, decimal separator, thousands separator all vary
Addresses: field order, required fields, and format vary significantly — use a locale-aware address form library

Design System Implications

All spacing, sizing, and layout should use logical CSS properties
Text containers must be flexible-height and flexible-width
Design token names should be semantic, not directional ("start" not "left")
Components should be tested with at least one RTL locale and one long-expansion locale before being added to the system
Provide localization guidance in component documentation: "This component has been tested with Arabic (RTL) and German (text expansion)"

Best Practices

Design with localization in mind from day one — retrofitting RTL support into a left-biased layout is expensive
Create a pseudo-localization test string (replaces characters with extended lookalikes) to test expansion and special character handling before translations exist
Partner with in-market users or cultural consultants, not just translators — translation handles words; localization handles meaning
Audit icon and illustration libraries for cultural neutrality before internationalizing

Frequently asked questions

What does the Localization Design AI skill do?

Why use Localization Design on TypingMind?

Because you install it once and use it with any model. Localization Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Localization Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/designer-skills/tree/main/design-systems/skills/localization-design. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Localization Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Localization Design?

As many as you like. As long as a model supports skills, you can use Localization Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Localization Design AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Agent Development

anthropics

OrganizationPopular

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors",…

Skill Development

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill…

Ponytail

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the…

Autoplan

Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Localization Design

What You Do

Text Expansion

RTL (Right-to-Left) Support

Typography for Non-Latin Scripts

Cultural Considerations

Color

Iconography

Date, Time, and Number Formats

Design System Implications

Best Practices

Frequently asked questions

Related AI Skills

Set up your own AI workspace now