Skip to content
Back to skills

Vscode Ext Localization

ASecurity

Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices

  • 38,521 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
ai-agentsjavascripttypescriptgojava

Works with

  • vscode

Security analysis

A100/100

Scanned June 6, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Vscode Ext Localization?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vscode Ext Localization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/github-vscode-ext-localization/badge)](https://www.skillsdirectory.com/skills/github-vscode-ext-localization)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…