vscode-ext-localization

Localize VS Code extension resources like package.json for multiple languages.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jmolz/m0lz.02 --skill vscode-ext-localization-jmolz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-ext-localization
Source: https://github.com/jmolz/m0lz.02/tree/main/.agents/skills/vscode-ext-localization
Command: npx skills add https://github.com/jmolz/m0lz.02 --skill vscode-ext-localization-jmolz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexity of localizing VS Code extensions, providing guidelines and instructions to ensure proper localization according to best practices.

Core Features & Use Cases

  • Guidelines for Localization: Offers detailed guidelines for localizing VS Code extensions.
  • Resource Localization: Helps in localizing configurations, commands, menus, views, and messages.
  • Use Case: If you're developing a VS Code extension and need to support multiple languages, this Skill will assist you in the localization process.

Quick Start

Use the vscode-ext-localization skill to localize the 'package.json' and related resources for the 'my-extension' extension.

Frequently Asked Questions about vscode-ext-localization

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

FAQPage Schema
How do I add language support to a VS Code extension?

To add language support, you need to localize your VS Code extension by following specific guidelines for translating configurations, commands, menus, and messages. This ensures your package.json and related resources adapt to multiple languages.

What is the best way to localize package.json for VS Code extensions?

The best way to localize package.json for VS Code extensions is to apply established localization guidelines that properly map configuration strings. This process ensures your extension's commands and views display correctly across different languages.

Does VS Code extension development require specific steps for resource localization?

Yes, VS Code extension development requires specific steps for resource localization to properly translate views and messages. Following these guidelines ensures your extension adheres to the platform's native multi-language support standards.

Can I use standard VS Code libraries to handle extension localization?

Yes, you can use standard VS Code libraries to handle extension localization. Adhering to VS Code's development guidelines and libraries ensures your package.json configurations and localized messages integrate seamlessly with the platform.

Why does my VS Code extension not display translated menus correctly?

Your VS Code extension might not display translated menus correctly if you did not follow proper localization guidelines for your resources. Ensuring strict adherence to VS Code's development libraries fixes these configuration and message mapping issues.