Tools and instructions for localizing settings, commands, and UI strings in VS Code extensions.
Install
mkdir -p .claude/skills/vscode-ext-localization && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/540" && unzip -o skill.zip -d .claude/skills/vscode-ext-localization && rm skill.zipInstalls to .claude/skills/vscode-ext-localization
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practicesKey capabilities
- →Generate package.nls localization bundles
- →Structure markdown walkthrough localization files
- →Map source code strings to l10n bundles
- →Manage configuration schema translation files
How it works
It enforces strict file-naming conventions and structure for language-specific translation bundles as required by the VS Code architecture.
Inputs & outputs
When to use vscode-ext-localization
- →Localize extension commands and settings
- →Translate markdown walkthrough content
- →Implement l10n bundles for extension messages
About this skill
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.
- Configurations like Settings, Commands, Menus, Views, ViewsWelcome, Walkthrough Titles and Descriptions, defined in
package.json-> An exclusivepackage.nls.LANGID.jsonfile, likepackage.nls.pt-br.jsonof Brazilian Portuguese (pt-br) localization - Walkthrough content (defined in its own
Markdownfiles) -> An exclusiveMarkdownfile likewalkthrough/someStep.pt-br.mdfor Brazilian Portuguese localization - Messages and string located in extension source code (JavaScript or TypeScript files)
-> An exclusive
bundle.l10n.pt-br.jsonfor Brazilian Portuguese localization
When not to use it
- →Localizing non-VS Code applications
- →When extension lacks user-facing strings
Limitations
- →Manual translation of content is still required
- →Complex UI layouts may break during localization
How it compares
It follows the specific VS Code framework for resource localization rather than using general i18n libraries.
Compared to similar skills
vscode-ext-localization side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vscode-ext-localization (this skill) | 5 | 7mo | No flags | Beginner |
| markdown-to-html | 16 | 6mo | Review | Beginner |
| browser-extension-developer | 4 | 6mo | No flags | Intermediate |
| add-i18n-locale | 0 | 2mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by github
View all by github →You might also like
markdown-to-html
github
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
browser-extension-developer
yamadashy
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
add-i18n-locale
GXFG
NaiveTab 浏览器扩展的 i18n 国际化开发指南。当用户要新增/修改翻译文本、添加多语言 key 时使用。涵盖中英文同步更新规则、变量替换模式等,防止遗漏或格式错误。
vue-i18n-skilld
skilld-dev
Internationalization plugin for Vue.js. ALWAYS use when writing code importing \"vue-i18n\". Consult for debugging, best practices, or modifying vue-i18n, vue i18n.
i18n
Project-N-E-K-O
i18n (internationalization) toolkit for projects using i18next. Provides three main functions: (1) i18n-check - Detect hardcoded Chinese text in HTML/JS files, (2) i18n-fix - Replace hardcoded text with i18n markers, (3) i18n-sync - Align translation keys across multiple languages (zh-CN, zh-TW, en,
harden
Aixbox
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.