skills.rest
vTRKA
vTRKACOMMUNITY
Explore all skills by this author →
GitHub

chrome-extension-build

Build and package Chrome MV3 extensions with bundler selection and CWS validation.

Updated Apr 27, 2026
Search Tags:#bundler#manifest validation#chrome-extension#mv3#hmr#cws packaging#web-ext lint
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill chrome-extension-build
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chrome-extension-build
Source: https://github.com/vTRKA/supervibe/tree/main/skills/chrome-extension-build
Command: npx skills add https://github.com/vTRKA/supervibe --skill chrome-extension-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Chrome extension builds often turn into a confusing, evidence-poor process where bundler choices, security constraints, lint warnings, and CWS packaging changes aren’t clearly validated before shipping.

Core Features & Use Cases

  • Bundler selection and wiring: Choose Vite+CRXJS, WXT, Plasmo, or no-bundler flow and configure the build pipeline accordingly, including popup HMR when relevant.
  • CWS-ready packaging with hard validation: Generate/verify icons, validate MV3 manifest properties, enforce permission/host permission checks, run web-ext lint as warnings-as-errors, and zip the correct dist output.
  • Durable handoff planning: Produces a build-pipeline decision that is bounded by required evidence, confidence scoring, and explicit stop conditions.

Quick Start

Ask your AI tool to set up the build pipeline for your Chrome MV3 extension with linting and CWS zip validation: “Set up chrome-extension-build to produce a CWS-ready zip with web-ext lint warnings blocked.”

Frequently Asked Questions about chrome-extension-build

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

FAQPage Schema
How do I package a Chrome MV3 extension for the Web Store?▼

Packaging a Chrome MV3 extension involves generating build-time assets, validating the MV3 manifest properties, enforcing permission checks, running web-ext lint as warnings-as-errors, and zipping the dist output for the Chrome Web Store.

What is the best way to add HMR to a Chrome extension popup?▼

Adding popup HMR involves selecting and wiring an appropriate bundler like Vite+CRXJS, WXT, or Plasmo, and configuring the build pipeline to support hot module replacement during development.

How do I validate my MV3 manifest before publishing?▼

Validating an MV3 manifest before publishing requires enforcing permission and host permission checks, running web-ext lint with warnings-as-errors, and verifying generated icons to ensure CWS readiness.

Should I use Vite+CRXJS, WXT, or Plasmo for my MV3 extension?▼

Choosing between Vite+CRXJS, WXT, and Plasmo depends on your project needs; the appropriate bundler is selected and wired to configure the build pipeline, including popup HMR when relevant.

Why does my Chrome extension build fail CWS packaging validation?▼

Your Chrome extension build fails CWS packaging validation when required evidence or validator proof is missing, causing a BLOCKED state if manifest properties, permissions, or web-ext lint constraints are not satisfied.

Related Skills

Explore More Software Engineering Skills→
fanthusfanthus

chrome-extension

Create and modify Chrome extensions with Manifest V3 scaffolding and messaging.

Community
Basic
brianlovinbrianlovin
357

chrome-webstore-release-blueprint

Set up Chrome Web Store API release automation with credential and CI configuration.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
tenequmtenequm
32

chrome-extension-wxt

Build cross-browser extensions with WXT using Manifest V3.

Community
Advanced