vscode-extension-dev

Name: vscode-extension-dev
Availability: InStock
Author: acigap

Guide development and maintenance of the ESP32 Token Display VS Code extension.

Updated May 17, 2026

Search Tags:#typescript #vscode #packaging #extension #esp32 #webview #platformio

Ready to run

npx skills add https://github.com/Acigap/ESP32-Token-Display --skill vscode-extension-dev-acigap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vscode-extension-dev
Source: https://github.com/Acigap/ESP32-Token-Display/tree/main/.github/skills/vscode-extension-dev
Command: npx skills add https://github.com/Acigap/ESP32-Token-Display --skill vscode-extension-dev-acigap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers maintain and extend the ESP32 Token Display VS Code extension by providing structured guidance for configuration, UI changes, commands, builds, packaging, and installation workflows.

Core Features & Use Cases

Extension Architecture Guidance: Explains the roles of extension source files, configuration managers, relay handling, port detection, and generated build outputs.
Development Workflow Support: Guides editing, compiling, packaging, installing, and troubleshooting the VS Code extension lifecycle.
Use Case: A developer adding a new configuration tab or board-specific option can use this Skill to update the correct files, preserve existing behavior, and rebuild the extension successfully.

Quick Start

Use the vscode-extension-dev skill to help me modify the VS Code extension by adding a new configuration tab and rebuilding the extension package.

Frequently Asked Questions about vscode-extension-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I package and install a VS Code extension after modifying TypeScript sources?▼

To package and install a VS Code extension, you must update TypeScript sources, manage configuration files, and validate build workflows to generate installation-ready outputs. This process preserves extension architecture while applying UI or command changes.

Can I add a new configuration tab to a VS Code extension without breaking existing behavior?▼

Yes, adding a configuration tab requires updating the correct source files while preserving the extension architecture. You must modify the configuration manager and rebuild the extension package to ensure existing commands and UI remain functional.

What is the best way to handle board-aware development scenarios in a VS Code extension?▼

Board-aware development in a VS Code extension involves managing configuration handling and port detection specific to hardware platforms. You update TypeScript sources and configuration files to support board-specific options during the build workflow.

Does this VS Code extension development workflow support webview UI updates?▼

Yes, VS Code extension webview UI updates are supported through structured modification workflows. You edit TypeScript sources to adjust the webview rendering, manage configuration files, and validate the build to deploy the updated interface.

Why does my VS Code extension build fail after adding new commands?▼

Extension build failures after adding commands often stem from not preserving extension architecture or mismanaging configuration files. You must validate build and deployment workflows and ensure TypeScript sources are correctly compiled.

Do I need PlatformIO to develop an ESP32 VS Code extension?▼

PlatformIO is part of the ESP32 development ecosystem targeted by this VS Code extension workflow. You manage board-aware development scenarios and configuration handling that integrate with PlatformIO for compiling and deploying hardware-specific builds.