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

1. ONLY write source language strings — let Localhero.ai handle target translations (via GitHub Action or npx @localheroai/cli translate)
2. Read localhero.json to find the source locale, file paths, and patterns
3. Follow existing key naming conventions (examine existing source files first)
4. Use glossary terms correctly when writing user-facing strings
5. Match the project's tone and style when writing copy
6. Translations happen automatically when the PR is created (if Localhero.ai GitHub Action has been setup)

Workflow

When adding or modifying user-facing strings:

1. Check localhero.json for sourceLocale and translationFiles.paths
2. Review the glossary and settings below for context
3. Examine existing source files to understand key naming patterns
4. Add/modify keys in source locale files
5. Let Localhero.ai translate target files:
   • If .github/workflows/ contains a workflow referencing localhero — translations happen automatically on PR
   • Otherwise, suggest running npx @localheroai/cli translate to generate translations

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 conventions. Common patterns:

• Dot-separated namespaces: users.profile.title
• Grouped by feature/page: dashboard.welcome_message
• Action-oriented for buttons: actions.save, actions.cancel

Glossary

Use these terms consistently when writing user-facing strings:

!npx @localheroai/cli glossary --output json 2>/dev/null || echo '{"glossary_terms": []}'

Project Settings

!npx @localheroai/cli settings --output json 2>/dev/null || echo '{"settings": {}}'

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