vscode-ext-localization

Guide VS Code extension localization across settings, walkthroughs, and source-code messages.

Updated Mar 11, 2026

Search Tags:#vscode #localization #i18n #walkthroughs #extension-contributions #package.nls #bundle.l10n

Ready to run

npx skills add https://github.com/selfagency/agentsy --skill vscode-ext-localization-selfagency

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VS Code extension localization keeps your UI strings, configuration labels, and walkthrough content inconsistent across languages, which makes your extension feel incomplete or confusing for non-English users.

Core Features & Use Cases

Correct localization coverage: Ensures every localizable resource is translated for all currently available languages, including settings, commands, menus, views, walkthrough titles/descriptions, and walkthrough content.
Resource-type aware output: Separates localization into the right VS Code mechanisms—package.nls.<LANGID>.json for package.json-declared contributions, per-language walkthrough Markdown files, and per-language bundle.l10n.<LANGID>.json for code-displayed messages.
Practical maintenance workflow: Supports updating or creating localizable resources while keeping existing languages in sync.

Quick Start

Use the vscode-ext-localization skill to update the localization files for your extension after you add a new command, view, or user-facing message.

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 for multiple languages?▼

VS Code extension localization uses package.nls.<LANGID>.json for contributions, per-language walkthrough Markdown files, and bundle.l10n.<LANGID>.json for code-displayed messages to translate UI strings, configuration labels, and walkthroughs.

What is the best way to keep VS Code extension translations consistent across all available languages?▼

Maintaining consistent VS Code extension localization requires updating every localizable resource—including settings, commands, menus, views, and walkthrough content—so that translations stay complete and synchronized across all currently available languages.

How do I translate walkthrough content in VS Code extensions?▼

Translating walkthrough content in VS Code extensions requires creating per-language walkthrough Markdown files using the walkthrough/<step>.<LANGID>.md naming convention to ensure each language has localized step titles, descriptions, and content.

Do I need separate localization files for package.json contributions and source code messages in VS Code?▼

VS Code extension localization separates resources into package.nls.<LANGID>.json for package.json-declared contributions and bundle.l10n.<LANGID>.json for code-displayed messages, ensuring each VS Code localization mechanism receives the correct translated strings.

Can I update existing VS Code extension localization files without breaking current translations?▼

Updating VS Code extension localization files supports a practical maintenance workflow that keeps existing languages in sync, allowing you to add or modify localizable resources while preserving previously completed translations across all available languages.