browser-ext-creator

Generate MV3 Chrome and Firefox extension scaffolds with component templates.

1|Updated Dec 14, 2014
One-click install
npx skills add https://github.com/goldeneggg/dotfiles --skill browser-ext-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-ext-creator
Source: https://github.com/goldeneggg/dotfiles/tree/main/claude-linux/.claude/skills/browser-ext-creator
Command: npx skills add https://github.com/goldeneggg/dotfiles --skill browser-ext-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

ブラウザ拡張機能の設計・実装を統合的に支援します。Chrome (Manifest MV3) と Firefox 対応の拦張を、要件定義からコード雛形まで一貫して作成できるようにします。

Core Features & Use Cases

  • Chrome/Firefox対応の設計テンプレートを提供し、Manifest V3 に基づく拡張機能の構造を自動生成します。
  • 実装テンプレートとして content-script.js、background.js、popup UI などの基本コンポーネントを含む雛形を提供します。
  • リファレンスとセキュリティガイドを統合し、セキュアなコーディングとベストプラクティスを案内します。

Quick Start

Provide your extension requirements and I will generate a MV3 Chrome/Firefox scaffold.

Frequently Asked Questions about browser-ext-creator

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

FAQPage Schema
How do I scaffold a Chrome extension with Manifest V3 compliance?

Scaffolding a Manifest V3 Chrome extension requires generating a deployment-ready file structure that includes content scripts, background service workers, and popup UI templates while enforcing MV3 compliance and secure coding guidelines.

Can I build a browser extension that works on both Chrome and Firefox?

Building a cross-compatible browser extension for Chrome and Firefox requires generating shared template assets and component structures that enforce MV3 compliance for Chrome while maintaining Firefox extension architecture compatibility.

What components are included in a standard web extension scaffold?

A standard web extension scaffold includes core component templates such as content-script.js for DOM manipulation, background.js for event handling, and popup UI files for user interaction, along with integrated reference assets for secure coding.

Does Manifest V3 affect how I structure background scripts in Firefox extensions?

Manifest V3 transitions background scripts to service workers in Chrome, but Firefox maintains its own compatibility approach, requiring scaffold templates that account for both browsers' specific background processing implementations.

What's the best way to ensure secure coding practices when developing browser extensions?

Ensuring secure coding practices involves following integrated security guides and reference materials that provide best-practice guidelines for content security policies, safe DOM manipulation, and secure extension architecture during scaffold generation.