skills.rest
mattmacleod16-svg
mattmacleod16-svgCOMMUNITY
Explore all skills by this author →
GitHub

vscode-ext-localization

Localize VS Code extension configurations, walkthroughs, and bundle strings.

1|Updated Feb 25, 2026
Search Tags:#localization#tooling#i18n#l10n#software-development#extensions#vs-code
One-click install
npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill vscode-ext-localization-mattmacleod16-svg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vscode-ext-localization
Source: https://github.com/mattmacleod16-svg/freedomforge-max/tree/main/.agents/skills/vscode-ext-localization
Command: npx skills add https://github.com/mattmacleod16-svg/freedomforge-max --skill vscode-ext-localization-mattmacleod16-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Localizes every aspect of a VS Code extension by generating or updating language-specific resources to reach a global audience.

Core Features & Use Cases

  • Configurations localization: translates settings, commands, menus, and views defined in package.json.
  • Walkthrough & content localization: localizes Walkthrough titles, descriptions, and Markdown content.
  • Messages & strings localization: provides per-language bundles for code-visible strings.

Quick Start

Create localized resources for your VS Code extension by adding the appropriate language files and referencing them in the codebase.

Frequently Asked Questions about vscode-ext-localization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I localize a VS Code extension for multiple languages?▼

VS Code extension localization involves creating language-specific resource files such as package.nls.LANG.json and bundle.l10n.LANG.json to translate settings, commands, menus, walkthroughs, and code-visible messages.

What aspects of a VS Code extension can be localized?▼

You can localize configurations like Settings, Commands, and Menus in package.json, alongside walkthrough content, Markdown files, and in-code message bundles to reach a global audience.

How do I translate VS Code extension settings and commands?▼

Translating VS Code extension settings and commands requires creating package.nls.LANG.json files to provide localized strings for configurations defined in package.json.

What files are needed for VS Code extension walkthrough localization?▼

Walkthrough localization in VS Code extensions uses dedicated walkthrough language files to translate titles, descriptions, and Markdown content while keeping resources synchronized.

How does string localization work for VS Code extension code?▼

String localization in VS Code extensions uses per-language bundles like bundle.l10n.LANG.json to provide translated code-visible strings for different languages.

Do I need separate language files for VS Code extension configurations and code strings?▼

Yes, you need separate files like package.nls.LANG.json for configurations and bundle.l10n.LANG.json for code strings to keep all language-specific resources synchronized.

Related Skills

Explore More Software Engineering Skills→
sandeepmvnsandeepmvn

vscode-ext-localization

Localize VS Code extension package.json, Markdown, and source code strings.

Community
Intermediate
selfagencyselfagency

vscode-ext-localization

Guide VS Code extension localization across settings, walkthroughs, and source-code messages.

Community
Basic
edjan11edjan11

vscode-ext-localization

Localize Visual Studio Code extensions across package.json, walkthroughs, and code strings.

Community
Basic
lehuuhau1231lehuuhau1231

i18n-localization

Detect hardcoded strings and manage translations for internationalization.

Community
Advanced