Handles react-i18next internationalization for LobeHub projects using a flat-key convention like `feature.context.action` instead of nested objects. Kicks in when you're adding user-facing strings, creating locale keys, or working with `useTranslation` hooks. The workflow is strict: edit only the TypeScript files in `src/locales/default/`, then run `pnpm i18n` to generate translations. It covers the full cycle from key naming to avoiding conflicts (don't use `clientDB.solve` as both a string and a prefix) to interpolation syntax with double curly braces. Opinionated but practical if you're working in the LobeHub ecosystem where consistency matters more than flexibility.
npx skills add https://github.com/lobehub/lobe-chat --skill i18n