VS Code extension localization

SkillDev tools

This skill gives your AI the official guidelines, libraries, and good practices for localizing VS Code extensions. Once added, it can translate your extension's settings, commands, and messages into multiple languages correctly. Your extension becomes usable in more languages without you needing to learn the localization rules yourself.

Available today. Use it from your connected AI after setup.

Add the skill, then ask your AI to localize your VS Code extension, mentioning which parts you want translated and the languages you want. You can also ask it to review and fix existing translations against the guidelines.

Then ask your AI: use the VS Code extension localization skill

What your AI can do with it

  • Translate extension settings into other languages
  • Translate commands and user-facing messages
  • Apply VS Code's extension development guidelines for localization
  • Use the recommended localization libraries
  • Follow localization good practices while it works

What this skill tells your AI

The instructions your AI receives, as published by muromi-rikka/folder-alias in .agents/skills/vscode-ext-localization/SKILL.md and read by ahel’s review.

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

Signals

GitHub stars
26
Forks
10
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
vscode-ext-localization
Source
github.com/muromi-rikka/folder-alias