skills/vscode-ext-commands/SKILL.md
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
npx skillsauth add alexandereiseghohi/comicwise vscode-ext-commandsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
development
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.
tools
Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices
tools
Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup.