5 个 · 按相关度排序
Manage multilingual interface text through translation keys. Follow the configured language list, reuse existing wording, update every locale, and regenerate and validate key types when adding text or translation modules.
中文简介正在准备中。当前显示英语简介。
Expert at building multi-language applications. Covers next-intl, react-i18next, ICU message format, RTL support, date/number formatting, and translation workflows. Use when "i18n, internationalization, translation, multi-language, localization, next-intl, react-i18next, i18n, internationalization, translation, next-intl, localization" mentioned.
中文简介正在准备中。当前显示原文说明。
Set up and audit multilingual application interfaces. Replace hard-coded text with translation keys, localize error messages, and check for missing translations, matching keys across languages, plural forms, and date or number formatting.
中文简介正在准备中。当前显示英语简介。
Takes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI translation. Use when the user asks to add or set up i18n, internationalization, localization, translations, or multi-language support, including phrasings like "add i18n", "internationalize my app", "make my app multilingual", "make my app translatable", "localize my app", "find hardcoded strings", "wrap my strings", and library-specific ones like "set up i18next", "add react-i18next", "use next-i18next". Also use when the user names languages they want to support ("I want German and French", "support more languages"), when an app already has i18next but strings are still hardcoded, or when translations need to move to a managed backend. Do not use for translating or reviewing strings in a project whose i18n is already set up.
中文简介正在准备中。当前显示原文说明。
Internationalize JavaScript apps with i18next. Use when adding translations, handling plurals, loading locale files dynamically, or i18n for React/Vue/Node.
中文简介正在准备中。当前显示原文说明。