localize

A guide to adapting products and services for people in different countries and cultures. Localization includes translation but also covers language direction, dates, payments, trust signals, colors, icons, and local expectations.

In plain words
What is it for?
Use it to plan international launches, review an existing product for localization readiness, support right-to-left languages, or design culturally appropriate checkout and navigation experiences.
Why use it?
It helps find problems that appear when a product is translated without changing the surrounding experience. This reduces the risk of confusing, inappropriate, or costly designs in new markets.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ghaida/intent/localize
Any agent
npx skills add ghaida/intent --skill localize
Clone the repo
git clone --depth 1 https://github.com/ghaida/intent

Made for: Claude Code, Codex.

Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00143 $0.03813
Opus 5 $0.00072 $0.01906
Sonnet 5 $0.00029 $0.00763
Haiku 4.5 $0.00014 $0.00381

Measured 2d ago against content hash 48fe07e0ab98, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

localize scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/localize/SKILL.md · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Localize — Design Across Cultures

Overview

Localization is not translation. Translation converts words; localization adapts the experience.

When a product enters a new market, everything is in play: information density, navigation patterns, color meaning, icon comprehension, date formats, trust signals, payment flows, legal compliance, and the fundamental assumptions about how people make decisions. A checkout flow designed for US consumers doesn't become a Japanese experience by translating the strings. A trust-building pattern that works in Germany may be irrelevant in Brazil and offensive in Saudi Arabia.

Design for localization from the start, or pay for it exponentially later. Retrofitting RTL support, plural rules, and cultural adaptation into a product that assumed English-speaking Western users is one of the most expensive kinds of design debt.

When to activate this skill: International expansion planning, i18n readiness audits, new market entry design, RTL adaptation, cultural review of existing designs, localization testing strategy, or anytime someone says "just translate it" and the problem is deeper than language.


Skill family

Localize works alongside the full Intent skill system:

  • /articulate: Everything they write will be localized. Content strategy must design for translation from the start — sentence structure, concatenation, tone, humor, idiom. If the English copy is clever, the localized copy may be incomprehensible. Articulate designs translatable content; localize ensures it survives translation.
  • /organize: Navigation and labeling may need cultural adaptation. Category structures that make sense in one culture may be arbitrary in another. Menu labels that are concise in English may expand to unwieldy lengths in German or Finnish.
  • /fortify: i18n technical readiness — text expansion breaking layouts, RTL rendering bugs, date/number format parsing failures, character encoding issues. Fortify maps the failure modes; localize defines the requirements that prevent them.
  • /strategize: Market analysis and audience definition per locale. Which markets, in what order, with what level of adaptation? /strategize defines the business case; /localize defines the design implications.
  • /investigate: Cultural research methods for unfamiliar markets. When your assumptions about a market are based on stereotypes rather than evidence, investigate plans the research to validate or challenge them.
  • /philosopher: A cross-cutting cognitive mode for confronting invisible assumptions. Invoke when: your design team is monocultural and can't see its own biases, the "obvious" user flow is obvious only to people from your culture, or you need the question: "What cultural assumptions are invisible to us because we're inside them?"

Read the full file on GitHub · 304 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 304 lines · 143 tokens per session scan A 48fe07e0ab98

Subscribe to this mod's changes

localize is a skill published in the GitHub repository ghaida/intent (139 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 143 tokens to every session and 3,813 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

amazon-global-selling

Evaluate and plan Amazon marketplace expansion across countries and regions. Use when a seller asks which Amazon marketplace to enter, how to compare international demand and economics, what tax, product-compliance, logistics, localization, account, or launch workstreams to investigate, or how to build a gated…

nexscope-ai/Amazon-Skills · 78 tokens

1688-Product-to-Ozon

将1688的商品铺货到俄罗斯电商平台Ozon(上架),通过Ozon官方API实现商品信息的上传和状态查询。适用于需要将单个1688的商品上架到Ozon的场景。.

LeoYeAI/openclaw-master-skills · 59 tokens

amazon-international-listings

Multi-marketplace listing management — translation, pricing localization, BIL (Build International Listings).

nexscope-ai/Amazon-Skills · 24 tokens

auditar-una-superficie

Califico una superficie de marketing específica y te doy una lista de arreglos priorizada. Elige qué auditar: la salud SEO de tu sitio, tu visibilidad en buscadores con IA como ChatGPT y Perplexity, una landing page evaluada en seis dimensiones, o un formulario que está perdiendo conversiones. Cada hallazgo está…

gethouston/houston · 84 tokens

frontend-design-deslop

Produce distinctive, non-generic UI and design applications well, working strategy-first. Identify the project (landing page, SaaS app, dashboard, ecommerce, presentation, docs, portfolio...) and its positioning and personality, commit to brand adjectives, translate into a typography and color system, then apply the…

samber/cc-skills · 223 tokens

b2c-localization

Add translations and multi-language support to B2C Commerce storefronts. Use this skill whenever the user needs to translate a storefront, add a new locale, create or edit .properties resource bundles, display translated strings in templates, format dates or currencies for different regions, or build a language…

SalesforceCommerceCloud/b2c-developer-tooling · 107 tokens