Summary

This skill provides guidelines for localizing VS Code extensions across three distinct resource types: package.json configuration metadata, walkthrough markdown content, and source code string messages. It documents the file naming conventions and directory structure required by VS Code's localization framework.

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

Use Cases

• Add localized settings to a VS Code extension
• Create translated walkthrough content for non-English markets
• Localize extension command and menu labels
• Implement string translations in TypeScript/JavaScript source code
• Update localization files when adding new extension features

Quality Notes

• Skill provides clear taxonomy of three localization approaches with file naming conventions
• Each approach is paired with concrete file path examples (package.nls.pt-br.json, walkthrough/*.md, bundle.l10n.json)
• Skill lacks implementation details: no guidance on how to extract strings, manage translation workflows, or handle pluralization/formatting
• No edge cases documented (e.g., what happens with dynamic strings, how to handle RTL languages, character encoding concerns)
• Missing error handling guidance — what to do if translations are incomplete or malformed
• Does not explain when to use each approach or provide decision criteria
• No reference to VS Code localization APIs, l10n module, or extension manifest localization fields
• Lacks examples of actual localization file structure and content
• Does not address testing localized extensions or validating translation completeness