skills.rest
TwuanMinn
TwuanMinnCOMMUNITY
Explore all skills by this author →
GitHub

browser-extension-builder

Design, implement, and publish MV3 cross-browser extensions for Chrome and Firefox.

Updated Jan 26, 2026
Search Tags:#chrome#cross-browser#manifest-v3#browser-extension#extension-development#mv3#firefox
One-click install
npx skills add https://github.com/TwuanMinn/fadelab --skill browser-extension-builder-twuanminn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-extension-builder
Source: https://github.com/TwuanMinn/fadelab/tree/main/.agent/skills/skills/browser-extension-builder
Command: npx skills add https://github.com/TwuanMinn/fadelab --skill browser-extension-builder-twuanminn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers design, implement, and publish cross-browser browser extensions that work reliably across Chrome, Firefox, and other engines, while navigating MV3 constraints, permissions, and store policies.

Core Features & Use Cases

  • Extension architecture and project structure compatible with MV3
  • Manifest v3 configuration, content scripts, background workers, and popup UI
  • Cross-browser publishing workflows including Chrome Web Store

Quick Start

Create a new MV3-compliant extension scaffold, implement core UI, and publish to the Chrome Web Store.

Frequently Asked Questions about browser-extension-builder

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

FAQPage Schema
How do I build a cross-browser extension that works with Manifest V3?▼

To build a cross-browser extension with Manifest V3, you need an MV3-compliant scaffold with clear manifest configuration, content scripts, background workers, and popup UI to ensure compatibility across Chrome and Firefox.

How do I set up background workers and content scripts for an MV3 extension?▼

Setting up background workers and content scripts for an MV3 extension requires configuring the manifest properly and structuring your project architecture to meet MV3 constraints and store policies.

What is the best way to publish a browser extension to the Chrome Web Store?▼

The best way to publish a browser extension to the Chrome Web Store is to follow a repeatable publishing workflow that ensures your MV3 configuration meets store acceptance requirements across Chrome and Firefox.

Does my cross-browser extension need a specific project structure to comply with MV3?▼

Yes, your cross-browser extension needs an MV3-compliant scaffold with a clear project structure to handle extension architecture, manifest configuration, and UI components reliably across Chrome and Firefox.

Why does my browser extension fail store acceptance under MV3 constraints?▼

Your browser extension may fail store acceptance under MV3 constraints if it lacks a repeatable publishing workflow, proper manifest configuration, or a compliant project scaffold for Chrome and Firefox compatibility.

Can I use the same manifest configuration for Chrome and Firefox MV3 extensions?▼

Yes, you can use a unified manifest configuration approach for cross-browser MV3 extensions, but you must navigate specific MV3 constraints and permissions to ensure compatibility and store acceptance across both Chrome and Firefox.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

trigger-setup

Initialize Trigger.dev with npx trigger init and generate trigger.config.ts.

Community
Intermediate
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

Browser Extension Builder

Build Chrome and Firefox browser extensions with Manifest V3.

Official
Intermediate
xkl2013xkl2013

modal

Create and manage modals, dialogs, and popups with imperative APIs.

Community
Intermediate
shiaho777shiaho777
5.5k

module-chrome-mv3

Scaffold a Chrome MV3 extension with manifest.json and content scripts for WebToApp's MV3 runtime.

Community
Intermediate