Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
Localize VS Code extensions across configurations, walkthrough content, and source code messages. Three localization approaches: package.nls.LANGID.json for settings, commands, menus, and views; markdown files for walkthrough content; bundle.l10n.LANGID.json for source code strings Covers all user-facing resources including contributed configurations, commands, menus, views, ViewsWelcome, and walkthrough titles and descriptions Requires creating or updating localization files for all supported languages whenever a localizable resource is added or modified 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.
don't have the plugin yet? install it then click "run inline in claude" again.