Vscode Ext Localization

Handles the three distinct localization approaches VS Code extensions require: package.json configurations through package.nls.LANGID.json files, walkthrough content via localized Markdown files, and source code strings using bundle.l10n.LANGID.json files. You'd reach for this when adding new languages to an existing extension or when building international support from scratch. It's solid on the mechanics of where each type of localizable content lives and how the file naming conventions work. The guidance covers the full scope from settings and commands to user-facing messages, which saves you from piecing together VS Code's somewhat fragmented localization docs.

skills.sh installs: 8.9K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill vscode-ext-localization --agent claude-code

Installs into .claude/skills of the current project.

Files

VS Code extension localization

This skill helps you localize every aspect of VS Code extensions

When to use this skill

Use this skill when you need to:

Localize new or existing contributed configurations (settings), commands, menus, views or walkthroughs
Localize new or existing messages or other string resources contained in extension source code that are displayed to the end user

Instructions

VS Code localization is composed by three different approaches, depending on the resource that is being localized. When a new localizable resource is created or updated, the corresponding localization for all currently available languages must be created/updated.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly