Workflows / Chrome extension
Build a Chrome extension with AI
Extensions live or die on permissions and review. This workflow asks for the minimum, keeps code small, and checks it against the Chrome Web Store rules before you submit.
The steps
Recommended tools link to their Agentdex pages. These are starting points, not rankings: pick what you already pay for.
Plan
The one job, and the exact permissions it needs.
Use
Claude Code. Useful for thinking through permissions and Manifest V3 limits before you code.Or try:
Cursor,
Gemini CLII want a Chrome extension that does [job]. List the Manifest V3 permissions it needs, why each one is needed, and how to avoid broad host permissions.
Build
A working popup, content script and service worker.
Use
Cursor. Multi-file edits fit the manifest, popup and scripts split well.Scaffold a Manifest V3 extension for this plan: manifest.json, popup (HTML/JS), content script and service worker. No frameworks. Comment each permission.
Test
It works on real sites and fails gracefully.
Use Playwright. Can load unpacked extensions in Chromium for automated tests.
Or try: Chrome DevTools,
Claude CodeWrite a Playwright test that loads this unpacked extension and checks the popup and the content script on a sample page.
Ship
A store listing and privacy answers that match the code.
Use
Claude Code. Good for drafting listing copy and privacy disclosures from your actual code.Or try:
GitHub CopilotRead the code and write the Chrome Web Store listing and the privacy practices answers. Only claim what the code actually does.
Maintain
Handle Chrome updates and user reports.
Use
GitHub Copilot. Stays in your editor and GitHub for quick patches.A user reports [bug]. Find the cause, fix it with the smallest change, and bump the version in manifest.json.