AutoGineer
Generated banner for Vscode Ext Localization
Generated logo for Vscode Ext Localization

Vscode Ext Localization

GitHubOfficialFirst committed by alefragnaniDistributed by GitHub

  • Skill
  • Guidelines
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
— the description by alefragnani

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides structured guidance on implementing localization for VS Code extensions. It outlines the specific file-based approaches required to translate user-facing elements, ensuring that extensions can support multiple languages effectively by following established development patterns.

What it does

  • Explains how to localize package.json contributions like settings, commands, and menus.
  • Details the process for localizing Markdown-based walkthrough content.
  • Provides instructions for managing string resources within JavaScript or TypeScript source code.
  • Defines the naming conventions for language-specific localization files.
  • Ensures consistency across different types of localizable extension resources.

When to use it

  • When preparing a VS Code extension for international distribution.
  • When adding new user-facing strings or UI elements to an existing extension.
  • When updating localized content for specific language identifiers.
  • When you need to verify the correct file structure for extension localization.

Advantages

  • Standardizes the localization workflow for VS Code extensions.
  • Reduces errors in resource file naming and organization.
  • Ensures all extension components, from settings to source code, are covered.
  • Aligns with official VS Code extension development practices.

Usage examples

“How do I localize a command title in my VS Code extension?”
The agent explains that you must define the translation in a package.nls.LANGID.json file corresponding to the target language.
“Where should I put translated strings for my TypeScript code?”
The agent instructs you to use a bundle.l10n.LANGID.json file to manage messages and strings located in your source code.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/vscode-ext-localization/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip vscode-ext-localization.zip -d .agents/skills

Documentation by alefragnani

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

Files

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of alefragnanialefragnani
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/vscode-ext-localization · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
alefragnani

AutoGineer is not affiliated with or endorsed by alefragnani or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download vscode-ext-localization.zip