Table of Contents
Quick Answer
Use Cursor or Claude Code to scaffold a Manifest V3 Chrome extension, then iterate with AI on content scripts, background service workers, and popup UI. Publish via the Chrome Web Store Developer Dashboard ($5 one-time fee).
- Total build time: 4-8 hours for a basic MVP
- Cost: $5 (Chrome Web Store fee) + AI tool subscription
- Skills needed: Basic JavaScript/HTML; AI fills the rest
What You'll Need
- Cursor IDE or Claude Code CLI
- Node.js 20+ and pnpm
- Chrome/Edge browser (dev mode enabled at chrome://extensions)
- $5 for Chrome Web Store developer account
- A clear idea of what the extension does (one sentence)
Steps
- Scaffold with AI. In Cursor, prompt: "Create a Manifest V3 Chrome extension that [your use case]. Include popup, content script, and background service worker." Let it generate manifest.json, popup.html, popup.js, content.js, and background.js.
- Configure manifest.json. Ensure manifest_version: 3, correct host_permissions, and action/popup wiring. Ask AI: "Audit my manifest.json for MV3 compliance and minimum permissions."
- Build the popup UI. Use Tailwind via CDN for speed. Prompt AI: "Add a React-free popup UI with a search input and results list, styled with Tailwind 3 CDN."
- Wire messaging. Content scripts can't call extension APIs directly — use chrome.runtime.sendMessage. Ask AI to generate a message-passing pattern between content.js and background.js.
- Load unpacked. Open chrome://extensions, enable Developer mode, click "Load unpacked", select your project folder. Test live.
- Package and publish. Zip your folder, upload to Chrome Web Store Dashboard↗, fill out listing, submit for review (3-7 days).
Common Mistakes
- Using Manifest V2: Deprecated since 2024. Always use V3.
- Over-requesting permissions: Google rejects extensions asking for <all_urls> without justification. Use activeTab where possible.
- Blocking the main thread in content scripts: Offload heavy work to the background service worker.
- Hardcoding API keys in content scripts: They're visible to every page. Route calls through your background worker.
Top Tools
Tool
Best For
Price
Cursor
Full IDE with inline AI
$20/mo
Claude Code
Terminal-native multi-file edits
$20/mo
Plasmo
Extension framework with hot reload
Free
CRXJS Vite Plugin
Vite + React for extensions
Free
Chrome Web Store
Distribution
$5 one-time
FAQs
Q: Do I need React for a Chrome extension?
No. Vanilla JS with Tailwind CDN works fine for most extensions and ships smaller bundles.
Q: How long does Chrome Web Store review take?
Typically 3-7 days for first submission; updates often review in under 24 hours.
Q: Can my extension call OpenAI or Claude APIs?
Route API calls through a backend you control. Never ship API keys inside the extension bundle.
Q: What's the difference between content scripts and background scripts?
Content scripts run in the context of web pages. Background (service worker) runs independently and has access to privileged Chrome APIs.
Q: Can I monetize my extension?
Yes — Stripe, Paddle, or a freemium model tied to a backend account. Chrome Web Store no longer handles payments directly.
Q: How do I test before publishing?
Load unpacked locally, then share the .zip with testers or use Chrome Web Store's unlisted/private distribution.
Conclusion
AI removes 80% of the boilerplate pain from Chrome extensions. Start with a tight one-sentence brief, let Cursor scaffold the bones, and iterate. Ship your first extension this weekend — read our guide on shipping MVPs fast.