Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

i18n-l10n

Estrelas0

Forks0

Atualizado21 de junho de 2026 às 08:29

Internationalizes and localizes products — strings, locales, formats, RTL, and translation workflow. Use when adding languages, fixing locale bugs, or expanding to non-English markets.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

vindreshsingh

vindreshsingh/engineering-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Designers de interfaces web e digitaisInformática e Matemática·SOC 15-1255

SKILL.md

readonly

name	i18n-l10n
description	Internationalizes and localizes products — strings, locales, formats, RTL, and translation workflow. Use when adding languages, fixing locale bugs, or expanding to non-English markets.

i18n / l10n

English-only caps your market. i18n (internationalization) makes the app locale-ready; l10n (localization) delivers each language correctly — including dates, numbers, currency, and layout direction.

Pairs with [[ui-craft]] for UI implementation, [[accessibility]] for RTL and language attributes, [[technical-writing]] for translated docs, and [[test-first]] for locale-specific tests.

When to Use

Adding a second language
Hard-coded strings in UI or API errors
Date/number/currency shown wrong in non-US locales
RTL language support (Arabic, Hebrew)
Translation workflow for releases

Skip for internal English-only tools with documented scope.

Process

1. Choose i18n architecture

Approach	Best for
Key-based JSON/PO files	Web (react-i18next, next-intl)
Platform native (Android strings.xml, iOS Localizable.strings)	Mobile
DB-backed strings	CMS-heavy, frequent copy changes

Rule: no user-facing string literals in components after i18n pass.

2. Extract and namespace strings

namespace.feature.element
auth.login.title
auth.login.submit
errors.network.timeout

Complete sentences in one key — don't split for grammar across keys
Interpolation for variables: "Hello, {{name}}"
Pluralization keys per ICU/plural rules

3. Locale formatting

Centralize:

Dates and times (timezone-aware)
Numbers and decimals
Currency (ISO 4217)
Relative time ("2 hours ago")

Test with de-DE, ja-JP, ar-SA at minimum.

4. RTL and layout

dir="rtl" on <html> or root when locale is RTL
Mirror icons that imply direction (arrows, back)
Don't mirror logos or media with text
Test [[accessibility]] with screen reader in target language

5. Translation workflow

Export strings (JSON/XLIFF)
Translate — human for marketing copy, MT+review for UI chrome OK
Import and verify in UI (pseudo-locale for overflow: [[!!]])
Lock strings before release; changelog for copy changes

6. Test per locale

All screens render without truncation/overflow
Plural forms correct (1 item vs 5 items)
Error messages translated
SEO: hreflang tags if public web ([[seo-growth]])

Common Rationalizations

"We'll translate when we have users there" — Retrofit i18n costs 3–5x vs building in.
"Google Translate in the UI" — Quality breaks trust; use proper workflow.
"English URLs are fine" — hreflang and locale paths matter for SEO.

Red Flags

Concatenated strings: "Hello " + name
Dates hard-coded as MM/DD/YYYY
Icons not mirrored in RTL
Missing translations fall back to empty string
Legal/compliance text machine-translated only

Verification

No hard-coded user-facing strings in changed files
Keys namespaced; plurals and interpolation correct
Formatting uses locale APIs
RTL tested if applicable
Translation export/import process documented
At least one non-English locale verified in browser

Mais deste repositório

mesmo repositório

skill-router

vindreshsingh/engineering-skills

Meta-skill that routes a task to the right engineering skill. Load this at the start of a session or when unsure which skill applies — it maps intent to the process that should govern the work.

2026-06-240

contract-testing

vindreshsingh/engineering-skills

Catches breaking changes between services before they ship, by testing the contract each consumer actually depends on instead of spinning up the whole system. Use when services deploy independently, when a provider API change could break a consumer, or when end-to-end integration tests are too slow and flaky to guard every service boundary.

2026-06-220

experimentation

vindreshsingh/engineering-skills

Proves whether a change actually moves the metric, with a valid A/B test instead of a guess — a hypothesis, a primary metric, a pre-computed sample size, guardrail metrics, and an honest readout. Use when shipping a change meant to improve a number (conversion, retention, performance), running an A/B or holdout, or deciding whether a feature "worked."

2026-06-220

feature-flags

vindreshsingh/engineering-skills

Decouples deploy from release using feature flags — ship code dark, roll out gradually, kill instantly, and remove the flag once it's done. Use when releasing risky or large changes, rolling out by percentage/cohort, delivering A/B variants, or when stale flags are accumulating as debt.

2026-06-220

threat-modeling

vindreshsingh/engineering-skills

Finds security risks at design time — before code exists — by mapping the system, enumerating how it could be attacked, and deciding what to do about each threat. Use when designing a feature that touches auth, data, money, or external input, when changing a trust boundary, or when a security-sensitive change needs a structured risk pass rather than a code-level review.

2026-06-220

agent-memory

vindreshsingh/engineering-skills

Designs durable, curated memory that an agent carries across sessions — what to persist, how to scope and retrieve it, and how to stop it from drifting or poisoning later runs. Use when an agent needs to remember decisions, preferences, or project facts beyond one context window, or when stale/over-generalized memory is corrupting its behavior.

2026-06-220