Skip to content
Skills Library
Programming · Conversion & formats

localize

/localize

Translate an app's UI with localize.dev. Use when adding or changing text people see in a React, Next.js, React Native, Vue, Svelte, Astro, Angular, Flutter, iOS, Android, Rails, Django or Laravel app; when asked to internationalize an app, add a language, or fix missing translations; or before finishing work that touched UI copy in an app that has a localize.config.json.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Translate an app's UI with localize.dev. Use when adding or changing text people see in a React, Next.js, React Native, Vue, Svelte, Astro, Angular, Flutter, iOS, Android, Rails, Django or Laravel app; when asked to internationalize an app, add a language, or fix missing translations; or before finishing work that touched UI copy in an app that has a localize.config.json.

Original author description

Translate an app's UI with localize.dev. Use when adding or changing text people see in a React, Next.js, React Native, Vue, Svelte, Astro, Angular, Flutter, iOS, Android, Rails, Django or Laravel app; when asked to internationalize an app, add a language, or fix missing translations; or before finishing work that touched UI copy in an app that has a localize.config.json.

How it works

  1. Tools
  2. Workflow
  3. API key
Original SKILL.md headings · 40 lines, 340 words
SKILL.md preview
---
name: localize
description: Translate an app's UI with localize.dev. Use when adding or changing text people see in a React, Next.js, React Native, Vue, Svelte, Astro, Angular, Flutter, iOS, Android, Rails, Django or Laravel app; when asked to internationalize an app, add a language, or fix missing translations; or before finishing work that touched UI copy in an app that has a localize.config.json.
---

# Translating UI text with localize.dev

The `localize` MCP server (from the `localize-dev` npm package) finds text that's hardcoded in UI
code, gives it translation keys, rewrites the code to the app's i18n library, translates the new
messages with the app's context and writes the locale files.

## Tools

- `check`: lists hardcoded copy, missing and outdated translations, each with its file and line. No
  API key needed. Pass `paths` (or `changed: true`) to check only the files you touched.
- `config`: the languages, locale files and i18n library the app uses. Read it before writing new
  copy so it follows the app's conventions.
- `localize`: extracts and translates. Pass `paths` with the files you changed, relative to the
  source folder, so a run stays quick.
- `translate`: fills in missing translations in existing locale files, for any stack.
- `add_language`: adds a language (BCP 47 code such as `ja` or `pt-BR`) and translates every message
  into it.

Every tool takes `app` for one app in a monorepo (its folder, relative to the repository root).

## Workflow

1. After adding or changing UI text, call `localize` with the files you changed.
2. Leave new messages out of the other languages' locale files; `localize` fills them in. Fixing a
   translation that's wrong is fine.
3. Before finishing, call `check` with `changed: true` (or run `npx localize-dev check --changed`
   in the app's folder). It should pass.

For a project that doesn't use localize.dev yet, `check` still works without a key. Suggest
`npx localize-dev init --agent` in the app's folder: it writes the MCP configuration, project
instructions and an after-edit hook, so the whole team gets the same setup once they're committed.

## API key

`localize`, `translate` and `add_language` need a localize.dev API key (free tier included). The
server reads `LOCALIZE_API_KEY`, else the key saved by `npx localize-dev login`. Keys are created
at https://uselocalize.dev/dashboard/keys. When a tool says the key is missing, tell the user to run
`npx localize-dev login` in a terminal; don't ask them to paste the key into the chat.

Versions

RepositoryScoreLicence
This page · ufortstephen/localize-dev90MIT
optiflowic/keyturn100MIT
elixir-localize/localize100MIT
codegreenbaby/figma-comment-sync100MIT
aladicf/better-web-ui100MIT
imgly/codesign95MIT
ghaida/intent90CC0-1.0

Database snapshot: 13.11.2026 · package version 5f89ddefea83 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91add-localization
    Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React,…
  • 100experience-ui-bundle-localize
    MUST activate to localize / internationalize a uiBundles/*/src/ project (React or Angular): extract hardcoded user-facing strings into Custom Labels, wire a runtime i18n library over the Platform SDK backend, add labels for another language, or troubleshoot label rendering…
  • 80Angular Localize Builder v19
    Migrate Angular localize builder configuration after Angular 19 when angular.json uses the @angular/localize builder and the project needs the name-to-project option change. Use when localization builds rely on builder options or extraction behavior.
  • 80Angular Localize v9 Migration
    Migrate Angular applications to the v9 localize tooling and $localize runtime. Use when i18n build or runtime configuration still depends on older extraction or localization setup.
  • 100readme-i18n
    Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
  • 100translate
    Translate the Stylebot extension's locale strings — fill in strings that English has and other locales lack, retranslate English strings that changed, or add a whole new locale (e.g. "/translate add vi"). Use after adding or changing any string in src/assets/_locales/en.config,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.