From Napkin
Guides VS Code extension command contributions including naming conventions, visibility rules, localization, and side bar command patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/napkin:vscode-ext-commandsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps you to contribute commands in VS Code extensions
This skill helps you to contribute commands in VS Code extensions
Use this skill when you need to:
VS Code commands must always define a title, independent of its category, visibility or location. We use a few patterns for each "kind" of command, with some characteristics, described below:
Regular commands: By default, all commands should be accessible in the Command Palette, must define a category, and don't need an icon, unless the command will be used in the Side Bar.
Side Bar commands: Its name follows a special pattern, starting with underscore (_) and suffixed with #sideBar, like _extensionId.someCommand#sideBar for instance. Must define an icon, and may or may not have some rule for enablement. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to the view/title or view/item/context, we must inform order/position that it will be displayed, and we can use terms "relative to other command/button" in order to you identify the correct group to be used. Also, it's a good practice to define the condition (when) for the new command is visible.
npx claudepluginhub ani1797/forge --plugin copilot-sdk2plugins reuse this skill
First indexed Jun 6, 2026
Adds commands (menu items, toolbar buttons) to Visual Studio extensions using VisualStudio.Extensibility, VSIX Community Toolkit, or legacy VSSDK. Covers .vsct files, command handlers, and icon placement.
Guides VS Code extension development from scaffolding to Marketplace publication, covering webviews, TreeView, testing, and troubleshooting.
Guides localization of VS Code extensions: settings, commands, menus, walkthroughs, and source code strings using NLS and l10n bundles.