Vscode Ext Localization
Ship a VS Code extension with correct package.nls, walkthrough, and bundle.l10n files for every supported language.
Overview
vscode-ext-localization is an agent skill most often used in Build (also Launch distribution prep) that guides proper VS Code extension localization across package.json, walkthrough Markdown, and bundle.l10n source strin
Install
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-localizationWhat is this skill?
- Covers three VS Code localization paths: package.json contributions, walkthrough Markdown, and bundle.l10n for in-code s
- Requires syncing every new or updated string across all currently supported language IDs
- Maps Settings, Commands, Menus, Views, ViewsWelcome, and Walkthrough titles to package.nls.LANGID.json files
- Walkthrough steps use per-locale Markdown files such as walkthrough/someStep.pt-br.md
- Source messages use bundle.l10n.LANGID.json alongside JavaScript or TypeScript extension code
- 3 localization approaches: package.nls, walkthrough Markdown per locale, and bundle.l10n for source strings
Adoption & trust: 8.7k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Who is it for?
Solo builders shipping or updating a VS Code extension who already support multiple locales and need the correct nls and l10n file layout per change.
Skip if: Teams that only need generic i18n advice for web apps, or extensions with no contributed commands, settings, walkthroughs, or user-visible code messages.
When should I use this skill?
Localizing new or existing contributed configurations, commands, menus, views, walkthroughs, or user-facing messages in extension source code.
What do I get? / Deliverables
After the skill runs, each localizable resource has matching package.nls, walkthrough locale Markdown, and bundle.l10n entries for every language you support.
- package.nls.LANGID.json files per locale
- Localized walkthrough Markdown per language
- bundle.l10n.LANGID.json string catalogs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Localization work happens while building and maintaining the extension artifact, before wider distribution. Docs and user-facing strings in package.json, Markdown walkthroughs, and TS/JS bundles are documentation and i18n deliverables tied to the extension package.
Where it fits
Add Brazilian Portuguese package.nls.pt-br.json when introducing new contributed commands in package.json.
Create walkthrough/someStep.pt-br.md after writing a new onboarding walkthrough step in English.
Expand marketplace locale coverage before publishing an extension update to non-English users.
How it compares
Use instead of guessing file naming for VS Code’s split nls versus l10n model when localizing marketplace extensions.
Common Questions / FAQ
Who is vscode-ext-localization for?
It is for solo and indie VS Code extension authors who must keep Settings, commands, menus, views, walkthroughs, and in-code messages localized for every language they ship.
When should I use vscode-ext-localization?
Use it during Build when adding package.json contributions or walkthroughs, when editing user-visible strings in TypeScript or JavaScript, and again before Launch when expanding locale coverage for marketplace users.
Is vscode-ext-localization safe to install?
It is procedural documentation for file layout and localization patterns; review the Security Audits panel on this Prism page before installing any parent skill pack from the catalog.
SKILL.md
READMESKILL.md - Vscode Ext Localization
# 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. 1. Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in `package.json` -> An exclusive `package.nls.LANGID.json` file, like `package.nls.pt-br.json` of Brazilian Portuguese (`pt-br`) localization 2. Walkthrough content (defined in its own `Markdown` files) -> An exclusive `Markdown` file like `walkthrough/someStep.pt-br.md` for Brazilian Portuguese localization 3. Messages and string located in extension source code (JavaScript or TypeScript files) -> An exclusive `bundle.l10n.pt-br.json` for Brazilian Portuguese localization