i18n

This skill is a repository-specific internationalization convention guide for LobeHub's lobe-chat project, which uses react-i18next with English (en-US) as the default language. It documents exactly where and how to add and edit user-facing strings so that contributors and AI agents follow the project's established i18n workflow instead of hardcoding UI copy or editing the wrong files. The central rule is that only files in `packages/locales/src/default/` should be edited by hand, and generated locale JSON files under `locales/` should be left to automation.

The guide specifies the project's key-naming convention — flat keys with dot notation following a `{feature}.{context}.{action|status}` pattern rather than nested objects — and how to avoid key conflicts and use `{{variableName}}` interpolation parameters. Its workflow is concrete: add keys to the relevant default namespace file, export new namespaces in the default index, optionally hand-write en-US and zh-CN preview translations for development, and otherwise let the daily `auto-i18n.yml` GitHub workflow open an automated translation PR for all other locales. It notes that `bun run i18n` should be run manually only when translations are needed immediately, since it is slow and requires an `OPENAI_API_KEY`. Usage examples show the `useTranslation` hook, single- and multi-namespace access, and interpolation, along with a list of the most-used namespaces (common, chat, setting) and others.

The target users are contributors and coding agents working on the lobe-chat codebase who need to add or modify translatable strings correctly. It is a benign code-convention reference: it describes editing locale source files and running a project build/translation script, with no risky operations. The mention of an `OPENAI_API_KEY` is standard tooling configuration for the translation script.