roo-translation

Name: roo-translation
Availability: InStock
Author: zgsm-ai

Translate and localize CoStrict extension strings across multiple languages.

4.4k|196|Updated Apr 10, 2025

Search Tags:#localization #translation #i18n #internationalization #vscode extension #string management

Ready to run

npx skills add https://github.com/zgsm-ai/costrict --skill roo-translation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: roo-translation
Source: https://github.com/zgsm-ai/costrict/tree/main/.roo/skills/roo-translation
Command: npx skills add https://github.com/zgsm-ai/costrict --skill roo-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating and localizing strings for the CoStrict extension, ensuring consistent and accurate internationalization across multiple languages.

Core Features & Use Cases

Localization Management: Provides guidelines for adding new strings, translating existing ones, and updating translation files for both the core extension and WebView UI.
Brand Consistency: Ensures adherence to specific brand voice, tone, and word choice guidelines, including terms to keep in English.
Use Case: When a new language needs to be added to the CoStrict extension, this skill guides the developer through the process of identifying strings, translating them accurately, and validating the changes.

Quick Start

Use the roo-translation skill to add new English strings and then translate them to German.

Frequently Asked Questions about roo-translation

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

FAQPage Schema

How do I translate and localize strings for a VS Code extension?▼

To translate VS Code extension strings, you need to manage localization files for both the core extension and WebView UI, ensuring accurate internationalization across multiple languages. This involves identifying strings and updating translation files.

What is the best way to handle interpolation variables during i18n implementation?▼

Handling interpolation variables during i18n implementation requires careful management within the translation files to prevent syntax errors. You must preserve variable placeholders exactly as they appear in the original English strings during localization.

How do I add a new language to my extension's localization management workflow?▼

Adding a new language to your localization management workflow involves identifying untranslated strings, translating them according to brand voice guidelines, and validating the updated i18n files. You must also handle specific namespaces correctly.

Does string management for WebView UI require separate translation files?▼

String management for WebView UI requires separate translation files from the core extension to ensure accurate internationalization. Both layers must adhere to specific brand voice, tone, and terminology guidelines during the localization process.

When should I keep specific terms in English during extension localization?▼

You should keep specific terms in English during extension localization when adhering to brand voice and word choice guidelines. The skill provides specific terminology rules to maintain consistency across all translated languages.

Why does internationalization break after updating translation files?▼

Internationalization breaks after updating translation files when interpolation variables or namespaces are mishandled during the string translation process. Accurate i18n implementation requires preserving exact variable syntax and maintaining correct namespace mapping.