vscode-ext-localization — GitHub Copilot skill
Use it to localize user-facing text in VS Code extensions. It fits when you add translations or update existing ones.
npx skills add github/awesome-copilot --skill vscode-ext-localizationWhat vscode-ext-localization does
This skill helps localize user-facing parts of VS Code extensions. It covers configuration in package.json, along with separate walkthrough files and strings in JavaScript or TypeScript.
Settings and commands use package.nls.LANGID.json. Walkthrough text goes in its own Markdown file, while source strings go in bundle.l10n.LANGID.json. When a localizable resource is added or changed, update its translation for every currently available language.
Install it if you maintain localization for a VS Code extension. It is not meant for work outside that task.
What it helps with
- translate extension settings from
package.json - prepare localized text for a walkthrough
- add translations for user-facing source strings
- update translations after changing a resource
Example prompts for the agent
- Localize the new setting and command in `package.json` for the available languages.
- Prepare translations for this walkthrough text and its source strings.
How to install vscode-ext-localization
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill vscode-ext-localization2GitHub CLI
gh skill install github/awesome-copilot vscode-ext-localization3Manually: put the files in place
.github/skills/vscode-ext-localization/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill vscode-ext-localization -a claude-code2Manually: put the files in place
~/.claude/skills/vscode-ext-localization/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vscode-ext-localization/
Manually: put the files in place
.agents/skills/vscode-ext-localization/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/vscode-ext-localization/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/vscode-ext-localizationManually: put the files in place
.devin/skills/vscode-ext-localization/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about vscode-ext-localization
How do I install vscode-ext-localization in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill vscode-ext-localization.
What does vscode-ext-localization do?
It guides you through localizing user-facing parts of a VS Code extension and choosing where translation files belong.
Which files should I use for translations?
Settings and commands use package.nls.LANGID.json. Walkthrough text goes in a separate Markdown file, while source strings use bundle.l10n.LANGID.json.
Source text
SKILL.md · MIT
--- name: vscode-ext-localization description: 'Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices' --- # 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
© github · MIT · github/awesome-copilot