Chrome Extension Builder
harry-harish/chrome-extension-builder
Construa e lance extensões Chrome MV3 sem armadilhas de configuração
Ver no GitHubPlugin para Claude Code que automatiza construção, validação e publicação de extensões Chrome Manifest V3. Scaffolda projetos, audita manifests, aplica validações de segurança (CSP, permissões) e prepara artefatos para Chrome Web Store, suportando WXT, Plasmo, CRXJS e setups vanilla.
Instalação
npx convez-ai harry-harish/chrome-extension-builder1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Scaffolding automatizado de novas extensões Chrome com estrutura validada
- Auditoria de manifests e detecção de problemas de CSP e permissões
- Migração de extensões Manifest V2 para V3 com plano detalhado
- Adição de componentes (popup, options page, content script, side panel) com segurança
Veredito

Ferramenta sólida que remove fricção real do desenvolvimento de extensões Chrome, com rails de segurança bem pensados (validações pós-mudança, confirmação em publicações). Recomendado para quem constrói extensões com frequência.
README
A tradução para o português deste README ainda está na fila.
Chrome Extension Builder
A Claude Code plugin for building and shipping Manifest V3 Chrome extensions without tripping over the usual stuff: manifest quirks, permission sprawl, CSP mistakes, broken builds, and Web Store submission prep.
It scaffolds new extensions, audits existing ones, adds common extension surfaces, runs validation, and prepares release artifacts. It works with WXT, Plasmo, CRXJS, and vanilla setups, with WXT as the default path.

Install
Inside Claude Code:
/plugin marketplace add harry-harish/chrome-extension-builder
/plugin install chrome-extension-builder@chrome-extension-builder-marketplace
For local development:
git clone https://github.com/harry-harish/chrome-extension-builder
claude --plugin-dir ./chrome-extension-builder
Start here
/chrome-ext:new
That launches a guided workflow for planning, scaffolding, validating, testing, and preparing an MV3 extension for release.
Why this exists
Building the feature is usually not the hardest part of extension work.
The time sink is everything around it: choosing the right framework, structuring background and content logic correctly, keeping permissions tight, satisfying MV3 rules, getting tests to pass, and cleaning things up for Chrome Web Store review. This plugin is built to handle that layer well.
Commands
/chrome-ext:new— Start a new extension with a guided multi-phase workflow./chrome-ext:validate— Run manifest, CSP, permission, and lint checks on the current project./chrome-ext:add-feature— Add a popup, options page, content script, side panel, devtools panel, or background handler./chrome-ext:publish— Prepare store assets, disclosure text, and packaged output for submission./chrome-ext:migrate-mv2— Audit an MV2 codebase and generate an MV3 migration plan.
Specialist agents
extension-architect— Chooses structure, capabilities, and framework direction.manifest-auditor— Reviewsmanifest.json, flags risky permissions, checks CSP, and rejects MV2-only patterns.extension-test-runner— Runs build, lint, and smoke-test workflows in isolation.
Safety rails
- A
PostToolUsehook re-checksmanifest.jsonchanges with manifest, CSP, and permission validators. If a critical issue appears, the session is pushed to fix it before moving on. - A
PreToolUsehook blocks live publish commands unless they are explicitly confirmed. - The plugin defaults to Manifest V3 only.
Framework support
- WXT — default recommendation
- Plasmo — supported
- CRXJS — supported
- Vanilla MV3 — supported
Use the one that matches your project. The plugin should help you move faster, not force a rewrite for style points.
Runtime requirements
- Node.js 18+
- pnpm, npm, yarn, or bun
- Python 3.10+ for validator scripts
- Playwright Chromium for E2E tests
- Optional GitHub and Chrome Web Store credentials for publishing flows
Defaults
- Manifest V3 only
- TypeScript-first output
chrome.activeTabpreferred over broad host permissions- Strict CSP, no remote code, no
eval - Reproducible builds
_locales-based i18n by default
What it checks
The validator path looks for problems that routinely waste time during extension development and review:
- Invalid MV3 manifest fields
- Overbroad or suspicious permissions
- CSP issues like
unsafe-inlineandunsafe-eval - Missing referenced files
- Old MV2 patterns that should not ship
- Packaging and lint problems that break release flow
Non-goals
This plugin does not:
- Guarantee Chrome Web Store approval
- Publish live by accident
- Make unsafe permissions acceptable
- Turn a weak product idea into a good extension
- Replace framework docs for WXT, Plasmo, or CRXJS
Known rough edges
- Firefox and Edge workflows are not the primary target yet.
- Existing repos with unusual layouts may need cleanup before automation works well.
- Store submission details can change faster than tooling does.
- Some UI and product decisions still need a human with taste.
A good fit
This plugin is useful if you are:
- Starting a new MV3 extension
- Migrating older extension code
- Adding features to an existing extension without breaking structure
- Preparing for Web Store submission and want stricter checks before upload
Repository structure
.claude-plugin/
agents/
commands/
hooks/
skills/
README.md
CHANGELOG.md
LICENSE
PRIVACY.md
Validate before release
/chrome-ext:validate
License
MIT