Manages react-i18next locale keys, namespaces, and translation workflows for LobeChat.
npx skills add https://github.com/SmallAi-API/smaihub --skill i18n-smallai-api
Please help me install this Agent Skill. Skill: i18n Source: https://github.com/SmallAi-API/smaihub/tree/main/.agents/skills/i18n Command: npx skills add https://github.com/SmallAi-API/smaihub --skill i18n-smallai-api
feature.context.action and {{variable}} interpolation, avoiding nested objects and key conflicts. - Namespace Workflow: Guides adding keys to packages/locales/src/default/, exporting namespaces, and previewing en-US/zh-CN translations manually. - Translation Pipeline Coordination: Clarifies when to rely on the daily auto-i18n.yml workflow versus running bun run i18n manually. - Use Case: When adding a new settings panel, use this Skill to create properly named keys in the setting namespace, wire up useTranslation in the component, and let the automated workflow handle remaining locales. ## Quick Start Ask the assistant to add a new translated string for a feature using the i18n conventions and show how to reference it with useTranslation.High-intent search queries and answers about installing and using this skill.
Add the key to the appropriate namespace file in packages/locales/src/default/ using flat dot notation like 'feature.context.action', then export the namespace from index.ts. Reference it in components with useTranslation and the t() function.
Pass an array of namespaces to useTranslation, such as useTranslation(['common', 'chat']), then prefix keys with the namespace like t('common:save'). Single-namespace usage only needs the namespace name as a string.
No, only edit files in packages/locales/src/default/. The JSON files in locales/ are generated, except hand-written en-US and zh-CN previews. Other locales are handled by the daily auto-i18n.yml workflow.
Run bun run i18n only when the branch needs translations immediately, since it is slow and requires an OPENAI_API_KEY. Otherwise, leave generated locales to the daily auto-i18n.yml workflow which opens an automated translation PR.
Conflicts occur when one key is a prefix of another, like 'clientDB.solve' and 'clientDB.solve.backup.title'. Resolve this by renaming the leaf key, for example 'clientDB.solve.action', so no key is both a value and a parent path.
OpenSourceAGIManages LobeHub locale keys and translations using react-i18next conventions.
andershi666Automate React translation management with flat dot-notation keys and locale exports.
cheafiTranslate Roo Code extension and WebView UI strings across multiple locales.
elcoospImplements LinguiJS i18n in JavaScript/TypeScript projects using @lingui/macro.