vscode-ext-localization

Localize VS Code extensions across package.json, walkthroughs, and in-code messages.

Updated Dec 14, 2025

Search Tags:#vscode #localization #i18n #translations #extension-development #package.nls.json #walkthroughs

Ready to run

npx skills add https://github.com/louisburroughs/durion --skill vscode-ext-localization-louisburroughs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vscode-ext-localization
Source: https://github.com/louisburroughs/durion/tree/main/.github/skills/vscode-ext-localization
Command: npx skills add https://github.com/louisburroughs/durion --skill vscode-ext-localization-louisburroughs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidelines to properly localize VS Code extensions, ensuring translations cover configurations (settings, commands, menus, views), messages in code, and walkthrough content across multiple languages.

Core Features & Use Cases

Localization strategy aligned with VS Code extension guidelines for configurations, content, and in-code strings.
Supports per-language files like package.nls.json, walkthrough translations, and bundle.l10n files to maintain consistency.
Use Case: A developer localizes a new extension for Spanish and Portuguese users, ensuring all commands and UI texts appear in the target languages.

Quick Start

Install or structure per-language localization files as described and run through a migration checklist to generate and validate translations for package.json, walkthroughs, and code messages.

Frequently Asked Questions about vscode-ext-localization

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

FAQPage Schema

How do I localize VS Code extensions using package.nls.json?▼

You localize VS Code extensions by maintaining separate language-specific package.nls.json files for settings, commands, and menus. This approach conforms to VS Code localization conventions without introducing runtime prompts or external fetches.

What is the best way to translate VS Code walkthrough content for multiple languages?▼

The best way to translate walkthrough content is by maintaining separate walkthrough translation files alongside bundle.l10n files. This ensures Markdown-based content and in-code messages are consistently localized across multiple target languages.

Does VS Code extension localization require external API calls or runtime prompts?▼

VS Code extension localization does not require runtime prompts or external fetches. You conform to VS Code localization conventions by maintaining static language-specific files like package.nls.json and bundle.l10n files directly in your project.

How do I translate in-code messages and package.json fields for a VS Code extension?▼

You translate in-code messages and package.json fields by applying a localization strategy that utilizes per-language files like package.nls.json and bundle.l10n files. This separates translatable strings from your core extension logic.

Can I use package.nls.json to localize VS Code extension commands and menus?▼

You can use package.nls.json to localize VS Code extension commands and menus. You maintain separate language-specific files to ensure all package.json configuration fields are translated into the target languages.