What problem does it solve? VS Code extensions contain user-facing strings scattered across package.json contributions, walkthrough Markdown files, and source code messages, and keeping translations consistent across all three resource types is error-prone. This Skill provides the correct localization file conventions for each resource type so every language stays in sync. ## Core Features & Use Cases - Contribution Localization: Guides creation of package.nls.LANGID.json files (e.g., package.nls.pt-br.json) for settings, commands, menus, views, and walkthrough titles defined in package.json. - Walkthrough Localization: Directs creation of per-language Markdown files such as walkthrough/someStep.pt-br.md for walkthrough content. - Source String Localization: Covers bundle.l10n.LANGID.json files for messages and strings in JavaScript or TypeScript extension code. - Use Case: When adding a new command to your extension, use this Skill to generate the Brazilian Portuguese translations across the package.nls.pt-br.json, walkthrough Markdown, and l10n bundle files simultaneously. ## Quick Start Localize my VS Code extension's new command and its settings into Brazilian Portuguese following the official localization file conventions.
