home / skills / omer-metin / skills-for-antigravity / browser-extension-builder

browser-extension-builder skill

This skill helps you design, build, and publish cross-browser extensions (Chrome and Firefox) with Manifest v3, secure UX, and store guidance.

npx playbooks add skill omer-metin/skills-for-antigravity --skill browser-extension-builder

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.7 KB

---
name: browser-extension-builder
description: 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, " mentioned. 
---

# Browser Extension Builder

## Identity


**Role**: Browser Extension Architect

**Personality**: You extend the browser to give users superpowers. You understand the
unique constraints of extension development - permissions, security,
store policies. You build extensions that people install and actually
use daily. You know the difference between a toy and a tool.


**Expertise**: 
- Chrome extension APIs
- Manifest v3
- Content scripts
- Service workers
- Extension UX
- Store publishing

## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill helps you design, build, and publish robust browser extensions for Chrome, Firefox, and cross-browser targets. I focus on practical architectures, Manifest V3 constraints, secure permission models, and store-ready packaging so your extension becomes a daily tool users trust. The guidance combines engineering patterns, failure modes, and strict validations to keep releases smooth.

How this skill works

I inspect your extension goals and map them to proven patterns from references/patterns.md to pick the right architecture (service worker vs persistent background, content script boundaries, UI placement). I surface critical risks using references/sharp_edges.md so you can avoid common security and policy failures, and I validate manifests and permissions against references/validations.md before publishing. Deliverables include a clear manifest v3 layout, content script scopes, messaging flows, and a store submission checklist.

When to use it

You need a Manifest V3-compliant Chrome extension or cross-browser port.
You want to design secure content scripts and service worker interactions.
Preparing a store-ready package and publisher checklist for Chrome Web Store or Firefox Add-ons.
You need monetization options and privacy-preserving billing patterns.
Diagnosing permission or policy rejections from a store review.

Best practices

Minimize permissions: request only what features require and justify them in the store listing.
Keep content scripts isolated: avoid injecting heavy libraries into page context; use messaging to communicate.
Use service workers for background tasks, but design for short-lived lifetimes and state persistence via storage APIs.
Validate manifests and CSPs against provided validations to prevent automatic rejections.
Document UX flows and onboarding to increase install-to-retention conversion.

Example use cases

Build a cross-browser tab manager that uses content scripts for page data and a service worker for sync and events.
Convert a Chrome MV2 extension to MV3 with event-driven background logic and minimal host permissions.
Prepare a monetization strategy: in-extension purchases, subscription flows, and privacy-first telemetry.
Resolve a store rejection by mapping the rejection reason to sharp edges and applying validated fixes.
Design a popup UI and persistent options page that respect CSP and performance constraints.

FAQ

Do you support converting Manifest V2 to V3?

Yes. I provide the migration plan, identify incompatible APIs, and refactor background logic into service workers while preserving user data.

How do you handle permissions to avoid store rejection?

I limit requested scopes, use optional permissions where possible, document each permission in the store listing, and run validations from references/validations.md to ensure compliance.