njust-ai-translation

Translate and localize NJUST_AI extension strings across core and WebView UI locales.

4|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/JunjieChen0/NJUST --skill njust-ai-translation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: njust-ai-translation
Source: https://github.com/JunjieChen0/NJUST/tree/main/.njust-ai/skills/njust-ai-translation
Command: npx skills add https://github.com/JunjieChen0/NJUST --skill njust-ai-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates and localizes NJUST_AI extension strings to enable multi-language support and consistent UI across Core and WebView.

Core Features & Use Cases

  • Guidelines for adding new languages and updating translations for core extension (src/i18n/locales/) and WebView UI (webview-ui/src/i18n/locales/).
  • Best practices for terminology consistency, file structure consistency, and following the project's i18n workflow.
  • Use cases include onboarding new languages, updating existing translations, and maintaining synchronized UI across components.

Quick Start

Identify the target language and apply translations to both core and WebView UI locale files using the existing i18n workflow.

Frequently Asked Questions about njust-ai-translation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new languages to an extension's i18n locales?

To update existing translations, modify the locale files in both src/i18n/locales/ and webview-ui/src/i18n/locales/ directories, ensuring terminology consistency and file structure alignment across the core extension and WebView UI components.

What is the best way to maintain terminology consistency during UI localization?

The best way to maintain terminology consistency during localization is to follow the project's i18n workflow guidelines, ensuring file structure consistency and synchronized UI translations across the core extension and WebView components.

Does the localization workflow cover both the core extension and WebView UI?

Yes, the localization workflow covers both the core extension and WebView UI, applying translated strings to locale files in src/i18n/locales/ and webview-ui/src/i18n/locales/ to maintain synchronized multi-language support.

When do I need to update webview-ui locale files for translation?

You need to update webview-ui locale files when adding new languages or updating translations, ensuring the WebView UI remains synchronized with the core extension's localized strings and overall i18n workflow.

Why does my localization workflow require updating multiple locale directories?

Updating multiple locale directories is required because the architecture separates core extension strings in src/i18n/locales/ from WebView UI strings in webview-ui/src/i18n/locales/, ensuring consistent multi-language UI across components.