skills/localheroai/localhero/SKILL.md
Manages i18n translations with Localhero.ai. Use when working with translation files, adding user-facing strings, or modifying UI copy.
npx skillsauth add aiskillstore/marketplace localheroInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
npx @localheroai/cli translate)localhero.json to find the source locale, file paths, and patternsWhen adding or modifying user-facing strings:
localhero.json for sourceLocale and translationFiles.paths.github/workflows/ references localheroai/localhero-action. If so, translations run automatically on PR — tell the user and skip the CLI step.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.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.
Before adding keys, examine existing source files to match the project's format and conventions.
JSON/YAML — nested or dot-separated keys:
users.profile.titledashboard.welcome_messageactions.save, actions.cancelPO/POT (gettext) — natural language source strings as keys:
msgid "Welcome to the dashboard"Run npx @localheroai/cli glossary --output json to get the project glossary. Use these terms consistently when writing user-facing strings.
Run npx @localheroai/cli settings --output json to get the project's tone, style, and language settings. Use these to match the expected voice.
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
See cli-reference.md for all available commands. Full source at https://github.com/localheroai/cli
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.