@github/vscode-ext-localization
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
No skills found in this collection.
SKILL.md
| name | vscode-ext-localization |
| description | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices |
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
Loading...
Select a file to preview
Analyzing security...
Checking scan reports and verification data.
Bill of Materials
Everything this skill can do — files, network, commands, and more.
No demos yet. To add one, ask your AI agent: "Submit a demo for @github/vscode-ext-localization" — or upload via the API.
To add a demo, ask your AI agent: "Submit a demo for @github/vscode-ext-localization"
No eval data yet. Eval results are published via the SkillSafe API.