Vscode ext localization

Skill github/awesome-copilot/skills/vscode-ext-localization

Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practicesFrom its SKILL.md

Install

npx -y skills add github/awesome-copilot --skill vscode-ext-localization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.4 KB, 261 tokens by cl100k_base, as published. Nobody here has run it

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.

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
Walkthrough content (defined in its own Markdown files) -> An exclusive Markdown file like walkthrough/someStep.pt-br.md for Brazilian Portuguese localization
Messages and string located in extension source code (JavaScript or TypeScript files) -> An exclusive bundle.l10n.pt-br.json for Brazilian Portuguese localization

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most translation skills give in 261 tokens

Counted across 286 of the 304 authors here whose files we hold, read 2026-09-06

Preserve all markdown formattingin 8 of 286, across 5 files
Use ICU message format for complex stringsin 8 of 286
Preserve all numbers, dates, and amounts exactlyin 7 of 286
Use CSS logical properties for RTL layoutsin 7 of 286
Format dates, numbers, and currencies with FormatStylein 7 of 286, across 6 files
Use locale-aware formatters for dates, numbers, and currencyin 7 of 286
Merge translated chunks in orderin 6 of 286, across 3 files
Use logical CSS properties instead of physical onesin 6 of 286
Use leading and trailing, never left and rightin 6 of 286, across 5 files
Use time-limited SAS URLs for document translationin 5 of 286, across 2 files
Split long content at markdown block boundariesin 5 of 286, across 2 files
Run first-time setup before any translation when preferences missingin 5 of 286, across 2 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.