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.
npx skills add https://github.com/github/awesome-copilot --skill vscode-ext-localization