Build cross-browser extensions (Chrome/Firefox) — Manifest V3 architecture, content scripts, service workers, popup UIs, monetization, and Web Store publishing. USE WHEN building, structuring, or publishing a browser extension.
Build cross-browser extensions (Chrome/Firefox) — Manifest V3 architecture, content scripts, service workers, popup UIs, monetization, and Web Store publishing. USE WHEN building, structuring, or publishing a browser extension.
cluster
frontend-web
version
1.0.0
origin
antigravity-awesome-skills (MIT)
source
vibeship-spawner-skills (Apache 2.0)
Browser Extension Builder
Upstream source: vibeship-spawner-skills (Apache 2.0) · packaged via antigravity-awesome-skills (MIT)
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.
Role: Browser Extension Architect
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.
{"manifest_version":3,"name":"My Extension","version":"1.0.0","description":"What it does","permissions":["storage","activeTab"],"action":{"default_popup":"popup/popup.html","default_icon":{"16":"icons/icon16.png","48":"icons/icon48.png","128":"icons/icon128.png"}},"content_scripts":[{"matches":["<all_urls>"],"js":["content/content.js"]}],"background":{"service_worker":"background/service-worker.js"},"options_page":"options/options.html"}
When to use: When modifying or reading page content
Content Scripts
Basic Content Script
// content.js - Runs on every matched page// Wait for page to loaddocument.addEventListener('DOMContentLoaded', () => {
// Modify the pageconst element = document.querySelector('.target');
if (element) {
element.style.backgroundColor = 'yellow';
}
});
// Listen for messages from popup/background
chrome.runtime.onMessage.addListener((message, sender, sendResponse) => {
if (message.action === 'getData') {
const data = document.querySelector('.data')?.textContent;
sendResponse({ data });
}
returntrue; // Keep channel open for async
});
// Use your backend for payments// Extension can't directly use Stripe// 1. User clicks "Upgrade" in popup// 2. Open your website with user ID
chrome.tabs.create({
url: `https://your-site.com/upgrade?user=${userId}`
});
// 3. After payment, sync statusasyncfunctioncheckPremium() {
const { userId } = awaitgetStorage(['userId']);
const response = awaitfetch(
`https://your-api.com/premium/${userId}`
);
const { isPremium } = await response.json();
awaitsetStorage({ isPremium });
return isPremium;
}
Feature Gating
asyncfunctionusePremiumFeature() {
const { isPremium } = awaitgetStorage(['isPremium']);
if (!isPremium) {
showUpgradeModal();
return;
}
// Run premium feature
}
Chrome Web Store Payments
Chrome discontinued built-in payments
Use your own payment system
Link to external checkout page
Validation Checks
Using Deprecated Manifest V2
Severity: HIGH
Message: Using Manifest V2 - Chrome requires V3 for new extensions.
Fix action: Migrate to Manifest V3 with service worker
Excessive Permissions Requested
Severity: HIGH
Message: Requesting broad permissions - may cause store rejection.
Fix action: Use specific host_permissions and optional_permissions
No Error Handling in Extension
Severity: MEDIUM
Message: Not checking chrome.runtime.lastError for errors.
Fix action: Check chrome.runtime.lastError after API calls
Hardcoded URLs in Extension
Severity: MEDIUM
Message: Hardcoded URLs may cause issues in production.
Fix action: Use chrome.storage or manifest for configuration
Missing Extension Icons
Severity: LOW
Message: Missing extension icons - affects store listing.
Fix action: Add icons in 16, 48, and 128 pixel sizes
1. Define extension functionality
2. Build popup UI with React
3. Implement content scripts
4. Add premium features
5. Publish to Chrome Web Store
6. Market and iterate
1. Design AI features for browser
2. Build extension architecture
3. Integrate AI API
4. Create popup interface
5. Handle usage limits/payments
6. Publish and grow
Related Skills
Works well with: frontend, micro-saas-launcher, personal-tool-builder
When to Use
User mentions or implies: browser extension
User mentions or implies: chrome extension
User mentions or implies: firefox addon
User mentions or implies: extension
User mentions or implies: manifest v3
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
