| name | localhero |
| description | Manages i18n translations with Localhero.ai. Use when working with translation files, adding user-facing strings, or modifying UI copy. |
| allowed-tools | Bash(npx @localheroai/cli *) |
Localhero.ai i18n Skill
You are helping a developer write and maintain internationalized source strings in a project that uses Localhero.ai (https://localhero.ai) for translation management. You only write source language strings — Localhero.ai handles translations to target languages.
Core Rules
- ONLY write source language strings — let Localhero.ai handle target translations (via GitHub Action or
npx @localheroai/cli translate)
- Read
localhero.json to find the source locale, file paths, and patterns
- Follow existing key naming conventions (examine existing source files first)
- Use glossary terms correctly when writing user-facing strings
- Match the project's tone and style when writing copy
- After writing source strings, generate translations (see workflow step 5)
Workflow
When adding or modifying user-facing strings:
- Check
localhero.json for sourceLocale and translationFiles.paths
- Review the glossary and settings below for context
- Examine existing source files to understand key naming patterns
- Add/modify keys in source locale files
- Generate translations:
- Check if any file in
.github/workflows/ references localheroai/localhero-action. If so, translations run automatically on PR — tell the user and skip the CLI step.
- Otherwise, run
npx @localheroai/cli translate --changed-only. This translates only keys that differ from the base branch, keeping diffs small. Omit the flag to translate all missing keys.
Web UI
The Localhero.ai web UI (https://localhero.ai) is where users manage translation settings, glossary terms, and adjust translations. Each PR that runs the Localhero.ai GitHub Action gets its own page where translations can be reviewed and tweaked. Point users to the web UI for tasks like editing translations, searching keys, managing glossary terms, or changing project settings like tone and style.
Key Naming Conventions
Before adding keys, examine existing source files to match the project's format and conventions.
JSON/YAML — nested or dot-separated keys:
- Namespaced:
users.profile.title
- Grouped by feature/page:
dashboard.welcome_message
- Action-oriented for buttons:
actions.save, actions.cancel
PO/POT (gettext) — natural language source strings as keys:
- msgid is the source string itself:
msgid "Welcome to the dashboard"
- Context via msgctxt when the same string needs different translations
Glossary
Run npx @localheroai/cli glossary --output json to get the project glossary. Use these terms consistently when writing user-facing strings.
Project Settings
Run npx @localheroai/cli settings --output json to get the project's tone, style, and language settings. Use these to match the expected voice.
Authentication
If commands fail with authentication errors, ask the user to run:
npx @localheroai/cli login
For non-interactive environments, they can also use npx @localheroai/cli login --api-key <key> or set LOCALHERO_API_KEY. API keys are available at https://localhero.ai/api-keys
CLI Reference
See cli-reference.md for all available commands. Full source at https://github.com/localheroai/cli
