vscode-extension-builder

VS Code Extension Builder

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "vscode-extension-builder" with this command: npx skills add prulloac/agent-skills/prulloac-agent-skills-vscode-extension-builder

VS Code Extension Builder

Overview

This skill guides the development of Visual Studio Code extensions by helping navigate the extensive VS Code Extension API documentation and providing structured guidance for common extension development tasks.

Documentation Base

All VS Code extension development guidance is based on the official documentation at: https://code.visualstudio.com/api

When assisting users, fetch relevant documentation pages to provide accurate, up-to-date information.

Official Documentation References

Your First Extension: https://code.visualstudio.com/api/get-started/your-first-extension

  • Step-by-step guide for scaffolding and running your first extension

  • Yeoman generator setup and project creation

  • Quick iteration with Extension Development Host

  • Essential debugging and testing techniques

Extension Anatomy: https://code.visualstudio.com/api/get-started/extension-anatomy

  • File structure and configuration explanation

  • package.json manifest details

  • Extension entry point (activate and deactivate functions)

  • Implicit activation events (VS Code 1.74.0+)

Wrapping Up: https://code.visualstudio.com/api/get-started/wrapping-up

  • Next steps after creating your first extension

  • Navigation to specialized guides and samples

  • Testing, publishing, and CI/CD resources

Core Workflow

  1. Understand User Intent

First, determine what the user wants to accomplish with their extension:

Common extension types:

  • Commands & UI extensions - Add commands, menus, keybindings, status bar items

  • Language support - Syntax highlighting, IntelliSense, diagnostics, formatting

  • Themes - Color themes, file icon themes, product icon themes

  • Webviews - Custom UI panels with HTML/CSS/JavaScript

  • Debuggers - Debug adapter integrations

  • Source control - SCM provider integrations

  • Tree views - Custom sidebar explorers

  • AI/Chat extensions - Chat participants, language model tools

  • Testing - Test provider integrations

  • Notebook support - Custom notebook renderers

  1. Fetch Relevant Documentation

Based on the user's intent, fetch the appropriate documentation:

For getting started (Getting Started Track):

For capability planning:

For specific features, use the extension guides:

For UX best practices:

For API reference:

For testing and publishing:

For advanced topics:

  1. Guide Implementation

After fetching documentation, provide step-by-step guidance:

  • Project setup - Use Yeoman generator or guide manual setup

  • Package.json configuration - Help define contribution points

  • Core implementation - Provide code guidance based on documentation

  • Testing - Help set up extension testing

  • Debugging - Guide F5 debugging setup

  • Publishing - Assist with vsce packaging

Quick Start Pattern

For new extensions, always start with:

Install dependencies (if needed)

npm install -g yo generator-code

Or use npx without global install

npx --package yo --package generator-code -- yo code

Guide users through the prompts based on their extension type.

Key Concepts to Explain

Activation Events

When extensions are loaded (see https://code.visualstudio.com/api/references/activation-events):

  • onCommand:

  • When a command is invoked

  • onLanguage:

  • When a file of specific language is opened

  • onView:

  • When a view is expanded

  • workspaceContains:

  • When workspace matches a pattern

  • onDebug

  • When debug session starts

  • On startup (use sparingly, impacts performance)

Important: Starting with VS Code 1.74.0, commands declared in contributes.commands automatically activate extensions without explicit onCommand entries.

Contribution Points

Static declarations in package.json that extend VS Code (see https://code.visualstudio.com/api/references/contribution-points):

  • commands

  • Define commands available in Command Palette

  • menus

  • Add commands to UI menus

  • keybindings

  • Define keyboard shortcuts

  • views

  • Create custom sidebar views

  • viewsContainers

  • Define view containers (sidebars, panels)

  • configuration

  • Define configuration settings

  • languages

  • Register new language support

  • grammars

  • Define syntax highlighting rules

  • themes

  • Register color themes

  • debuggers

  • Register debug adapters

  • snippets

  • Define code snippets

  • taskDefinitions

  • Define custom task types

  • semanticTokenTypes/Modifiers

  • Extend semantic highlighting

  • walkthroughs

  • Create interactive extension walkthroughs

  • notebookProvider

  • Register notebook renderers

  • customEditors

  • Register custom editor providers

Manifest Best Practices

For optimal marketplace presentation:

  • Use displayName and description clearly and concisely

  • Set categories from allowed values for better discoverability

  • Provide icon (PNG, 128x128 minimum) and galleryBanner for visual appeal

  • Include repository , bugs , and homepage in resources section

  • Use keywords array (up to 30) for search optimization

  • Set appropriate engines.vscode version (don't use * )

  • Configure extensionPack for bundling related extensions

  • Declare extensionDependencies if your extension relies on others

  • Mark capabilities for untrustedWorkspaces and virtualWorkspaces support

For pricing and availability:

  • Use pricing field (Free/Trial)

  • Set preview: true for beta extensions

  • Use preview for extensions not ready for production

Extension Anatomy

Understanding the core components of VS Code extensions:

File Structure:

. ├── .vscode │ ├── launch.json # Debug configuration for F5 debugging │ └── tasks.json # Build task configuration (TypeScript compilation) ├── .gitignore ├── README.md ├── src │ └── extension.ts # Main extension code (entry point) ├── package.json # Extension manifest └── tsconfig.json # TypeScript configuration

package.json - Critical Fields:

  • name

  • Extension identifier (lowercase, no spaces)

  • displayName

  • Human-readable name for Marketplace

  • version

  • SemVer version number

  • publisher

  • Publisher identifier

  • description

  • Short description of functionality

  • engines.vscode

  • Minimum VS Code version (e.g., "^1.80.0" )

  • main

  • Entry point to extension (compiled JavaScript)

  • browser

  • Entry point for Web extensions

  • activationEvents

  • When the extension is activated

  • contributes

  • Static declarations of extension capabilities

  • categories

  • Marketplace categories for discoverability

  • icon

  • Extension icon (128x128 pixels minimum)

  • license

  • License information

  • repository

  • Repository URL

Extension Entry File (extension.ts/js):

  • activate(context)

  • Called when extension activates; setup your extension here

  • deactivate()

  • Called when extension deactivates; clean up resources here

  • Disposables must be added to context.subscriptions for proper cleanup

Key Modern Features (VS Code 1.74.0+):

  • Implicit activation events: Commands declared in contributes.commands automatically activate extensions

  • No need for explicit onCommand activation events

  • Reduces startup impact by lazy-loading extensions only when needed

Common Patterns

Testing Your Extension

Modern testing approach using the VS Code Test CLI:

Install test dependencies

npm install --save-dev @vscode/test-cli @vscode/test-electron

Configuration (.vscode-test.js):

const { defineConfig } = require('@vscode/test-cli'); module.exports = defineConfig({ files: 'out/test/**/*.test.js' });

Run tests:

npm test

Key testing features:

  • Extensions run in Extension Development Host with full API access

  • Mocha test framework by default

  • Can debug tests with VS Code's debugger

  • Support for multiple test configurations

  • Workspace folder support during testing

  • CI/CD integration ready

See https://code.visualstudio.com/api/working-with-extensions/testing-extension for detailed setup.

Debugging Your Extension

Quick Debug with F5:

  • Open extension project in VS Code

  • Press F5 or run Debug: Start Debugging from Command Palette

  • Extension Development Host window opens with your extension loaded

  • Set breakpoints by clicking line numbers

  • Use Debug Console to evaluate expressions

  • Use Run and Debug panel to inspect variables

Key debugging features:

  • Full Node.js debugging capabilities

  • Hover over variables to see values

  • Watch expressions and call stacks

  • VS Code's built-in debugger works with extensions

Modern VS Code Features (1.74.0+)

Implicit Command Activation

  • Commands in contributes.commands auto-activate the extension

  • Reduces explicit configuration needed

  • Improves extension startup time

Web Extensions

Workspace Trust

AI and Language Model Integration

Extension Marketplace Features

  • extensionPack for bundling extensions

  • extensionDependencies for runtime dependencies

  • extensionKind for remote/local execution preference

  • Pricing models (Free/Trial)

  • Preview flag for beta releases

Common Patterns and Examples

Registering a Command

import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) { // Register a command - no explicit onCommand needed (VS Code 1.74.0+) let disposable = vscode.commands.registerCommand('extension.commandName', () => { vscode.window.showInformationMessage('Hello World!'); });

context.subscriptions.push(disposable);

}

export function deactivate() {}

In package.json:

{ "contributes": { "commands": [ { "command": "extension.commandName", "title": "My Command" } ] } }

Creating a Tree View

Provide hierarchical data in sidebar:

Building a Webview

Custom HTML UI for complex interfaces:

Language Server Protocol

For rich language support:

Storing Data

  • Global: context.globalState.update(key, value)

  • Workspace: context.workspaceState.update(key, value)

  • Configuration: vscode.workspace.getConfiguration()

Showing UI Elements

// Information message vscode.window.showInformationMessage('Message');

// Quick pick for selection const pick = await vscode.window.showQuickPick(['Option 1', 'Option 2']);

// Input box for text const input = await vscode.window.showInputBox({ prompt: 'Enter text' });

// Progress indication await vscode.window.withProgress({ location: vscode.ProgressLocation.Notification, title: 'Processing...' }, async (progress) => { // Long-running operation });

Documentation Navigation Strategy

  • Start broad - Fetch overview pages to understand scope

  • Go specific - Fetch detailed guides for the exact feature needed

  • Check references - Fetch API references for specific types/methods

  • Review examples - Point users to sample extensions at https://github.com/microsoft/vscode-extension-samples

Extension Capabilities and Restrictions

What Extensions Can Do

  • Extend VS Code UI (sidebars, panels, status bar, decorations, etc.)

  • Add commands and keybindings

  • Create custom views with TreeView API

  • Build custom UI with Webview API

  • Provide language features (IntelliSense, diagnostics, formatting, etc.)

  • Integrate debuggers and test frameworks

  • Add themes and icons

  • Register configuration settings

  • Contribute walkthroughs and tutorials

  • Integrate with Source Control providers

  • Build custom editors and notebooks

Important Restrictions

  • No DOM access - Cannot access VS Code's internal DOM directly

  • No custom CSS - Cannot inject custom stylesheets into VS Code UI

  • Runs in Extension Host - Extensions run in a separate process

  • Must use VS Code API - Cannot use undocumented internal APIs

  • Performance constraints - Heavy operations impact all extensions

Rationale: These restrictions ensure stability, performance, and security while allowing VS Code to evolve freely without breaking extensions.

Best Practices

Minimal Startup Impact

  • Use activation events wisely; avoid * unless necessary

  • Lazy-load dependencies and APIs

  • Rely on implicit activation for declared commands (VS Code 1.74.0+)

Resource Management

  • Always dispose of resources in deactivate() or add to context.subscriptions

  • Clean up event listeners, file watchers, and language clients

  • Prevent memory leaks by removing references

Type Safety

  • Use TypeScript for better developer experience

  • Install correct @types/vscode version matching engines.vscode

  • Enable strict TypeScript compilation

Error Handling

  • Catch and handle errors in command implementations

  • Provide meaningful error messages to users

  • Log errors to extension output channel for debugging

Performance

  • Bundle extensions for production (webpack/esbuild)

  • Use Tree Data Provider for large datasets with pagination

  • Minimize async operations in activation

UX Guidelines

Testing

Publishing

Progressive Assistance Levels

For Absolute Beginners

Goal: Get them building and debugging quickly

  • Guide through "Your First Extension" walkthrough

  • Explain the three core concepts:

  • Activation Events: When extension loads

  • Contribution Points: What the extension contributes to VS Code

  • VS Code API: How to interact with VS Code

  • Walk through Yeoman scaffolding step-by-step

  • Show how to modify the extension and test with F5

  • Explain package.json basics (name, version, main, engines)

  • Show how to register and run a command

Resources:

For Intermediate Users

Goal: Build feature-rich extensions independently

  • Fetch specific extension guide documentation

  • Explain API patterns and best practices

  • Guide through VS Code API exploration

  • Help with:

  • Configuration settings

  • File system operations

  • Tree views and sidebars

  • Webview implementation

  • Language features

  • Assist with debugging techniques and issue diagnosis

  • Help set up and run extension tests

Resources:

For Advanced Users

Goal: Build complex, production-grade extensions

  • Point to proposed APIs for experimental features

  • Help with Language Server Protocol integration

  • Guide multi-extension architecture

  • Assist with:

  • Remote and web extension support

  • Custom editors and notebooks

  • Advanced tree view providers

  • Semantic highlighting

  • Debug adapter integration

  • Help prepare for Marketplace publishing

  • Advise on CI/CD setup

Resources:

Reference Documentation

For comprehensive guides on specific extension types and advanced patterns, see:

  • Official Documentation Map - Complete map of VS Code Extension API documentation (https://code.visualstudio.com/api)

  • Extension Development Guide - Detailed guide for common extension patterns

  • API Quick Reference - Quick lookup for common VS Code APIs

Read these references when users need deeper guidance on specific topics or navigation help through the official documentation.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

Coding

github-pr-comments

No summary provided by upstream source.

Repository SourceNeeds Review
-12
prulloac
Coding

devcontainer-config

No summary provided by upstream source.

Repository SourceNeeds Review
-10
prulloac
Coding

github-create-issue

No summary provided by upstream source.

Repository SourceNeeds Review
-7
prulloac