skills.rest
enact-on
enact-onCOMMUNITY
Explore all skills by this author →
GitHub

browser-extension

Create cross-browser Manifest V3 extensions with TypeScript.

1|Updated Jan 16, 2026
Search Tags:#TypeScript#extension#devtools#browser#popup#content-scripts#MV3
One-click install
npx skills add https://github.com/enact-on/super-ai-github --skill browser-extension-enact-on
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-extension
Source: https://github.com/enact-on/super-ai-github/tree/main/.opencode/skill/browser-extension
Command: npx skills add https://github.com/enact-on/super-ai-github --skill browser-extension-enact-on

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers build robust cross‑browser extensions by providing a clear structure, MV3 patterns, and TypeScript-ready guidance, reducing setup time and boilerplate.

Core Features & Use Cases

  • MV3-ready architecture: manifests, background service workers, content scripts, and UI components that work across Chrome, Edge, Firefox.
  • TypeScript-first development: TS types, modern APIs, and a scalable file structure for popup, options, side panel, and devtools.
  • Use Case: Build a configurable extension with a popup UI, content scripting, and optional DevTools integration across multiple browsers.

Quick Start

Create a new browser-extension project following the skill's folder layout and implement a minimal MV3 extension (manifest.json, background service worker, popup UI) to verify cross-browser loading.

Frequently Asked Questions about browser-extension

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

FAQPage Schema
How do I build a cross-browser extension using Manifest V3 and TypeScript?▼

You structure cross-browser MV3 extensions using TypeScript by enforcing a modular folder layout with dedicated manifest, popup, content, and background worker directories to support Chrome, Edge, and Firefox.

What folder structure should I use for an MV3 browser extension?▼

An MV3 browser extension should use a modular folder structure with distinct directories for src, popup, content scripts, and background service workers, along with optional scripts, references, and assets as needed.

Can I use Manifest V3 service workers for extensions across Chrome, Edge, and Firefox?▼

Yes, Manifest V3 service workers are supported across Chrome, Edge, and Firefox by applying provided cross-browser patterns for background workers, content scripts, and UI components within your TypeScript project.

How do I add DevTools integration to a TypeScript browser extension?▼

You add DevTools integration by following TypeScript-first patterns and extending the modular project structure to include optional DevTools components alongside your standard popup and content scripts.

Do I need specific dependencies to start developing an MV3 extension with this approach?▼

No external dependencies are required to start developing an MV3 extension; this approach relies on a TypeScript-ready scalable file structure and standard browser APIs to reduce setup time and boilerplate.

Related Skills

Explore More Software Engineering Skills→
TheBushidoCollectiveTheBushidoCollective
187

typescript-type-system

Configure TypeScript strict mode, generics, type guards, and compiler options.

Official
Advanced
joeblackwaslikejoeblackwaslike

vscode-extension-builder-lawvable

Build, bundle, test, and package VS Code extensions into .vsix files.

Community
Advanced
cloud-native-toolscloud-native-tools

extension-e2e-test

Automate Chrome Manifest V3 extension end-to-end tests with Playwright.

Official
Advanced
mengxi-reammengxi-ream
9.0k

wxt

Build cross-browser extensions with WXT file-based entrypoints and manifest generation.

Community
Advanced