hot-reloading-for-chrome-extensions
Configures automated hot reloading for Chrome Extension development to bypass manual refresh cycles.
Install
mkdir -p .claude/skills/hot-reloading-for-chrome-extensions && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1942" && unzip -o skill.zip -d .claude/skills/hot-reloading-for-chrome-extensions && rm skill.zipInstalls to .claude/skills/hot-reloading-for-chrome-extensions
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Set up hot-reloading for chrome extensions. Provides a zero-dependency solution for automatic extension refreshing during development.Key capabilities
- →Monitor project directory for file changes
- →Broadcast reload signals via SSE
- →Inject client-side listeners into service workers
- →Refresh extension tabs and background scripts
- →Support Manifest V3 extension development
How it works
A Node.js watcher monitors files and broadcasts reload signals to an injected client script in the extension, which triggers a runtime reload.
Inputs & outputs
When to use hot-reloading-for-chrome-extensions
- →Setting up chrome extension development environment
- →Enabling auto-reload on file changes
- →Developing browser extensions
About this skill
Hot Reloading for Chrome Extension Development
Provide a zero-dependency hot-reloading system for Manifest V3 (MV3) extensions. This system enables automatic extension and tab refreshing whenever source files change, eliminating the need for manual reloads in chrome://extensions.
How It Works
The system consists of a server-side watcher and a client-side listener:
- The Watcher (Node.js): Runs on the developer's machine. It uses native
fs.watchto monitor the project directory and exposes a Server-Sent Events (SSE) endpoint (/events). When a file change is detected, it broadcasts a "reload" signal. - The Client (JavaScript): Injected into the extension's background service worker. It connects to the watcher server using
EventSource. Upon receiving a "reload" signal, it reloads any open extension tabs (options pages, popups) and then callschrome.runtime.reload()to refresh the extension itself.
Implementation Guide for the Agent
To implement hot reloading in the current project, follow these steps:
1. Copy the Source Files
Copy the following files from the skill's examples/ directory into the project root or a designated tools/ directory:
examples/hot-reload-server.mjs->hot-reload-server.mjsexamples/hot-reload-client.js->hot-reload-client.js
2. Configure the Background Script
Update the extension's background service worker (e.g., service-worker.js) to import the client script. This should be the first line in the file:
importScripts('hot-reload-client.js');
3. Update Permissions
Ensure the manifest.json includes management (to detect development mode) and tabs (to refresh open extension pages):
{
"permissions": [
"management",
"tabs"
]
}
4. Provide Execution Instructions to the User
Inform the user to start the watcher server in their terminal:
node hot-reload-server.mjs
Additional Resources
Examples
Working configuration and implementation scripts in examples/:
examples/hot-reload-server.mjs- The Node.js watcher server (to be copied to the project).examples/hot-reload-client.js- The extension-side client (to be copied to the project).
When not to use it
- →Production extension environments
- →Extensions not using Manifest V3
Prerequisites
Limitations
- →Requires manual setup of watcher and client scripts
- →Only supports Manifest V3
How it compares
It provides a zero-dependency automated reload mechanism, replacing the manual process of reloading extensions in the browser settings.
Compared to similar skills
hot-reloading-for-chrome-extensions side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| hot-reloading-for-chrome-extensions (this skill) | 4 | 2mo | Review | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| playwright-browser-automation | 29 | 7mo | Review | Intermediate |
| browser-daemon | 5 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by paulirish
View all by paulirish →You might also like
webapp-testing
anthropics
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.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
ai-organizer-ui-consolidation
thebearwithabite
Build a unified, ADHD-friendly web UI that consolidates 70+ CLI tools into a beautiful liquid glass interface for the AI File Organizer. Use when creating the complete frontend application that replaces all terminal interactions with a macOS-inspired dashboard for file organization, search, VEO prompts, and system management.
desktop
lobehub
Electron desktop development guide. Use when implementing desktop features, IPC handlers, controllers, preload scripts, window management, menu configuration, or Electron-specific functionality. Triggers on desktop app development, Electron IPC, or desktop local tools implementation.
browser-extension-builder
davila7
Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3.