browser-extension-engineering

Browser-extension-engineering team — 2 agents (extension-architect, extension-implementation-engineer) for building, shipping, and maintaining cross-browser extensions on Manifest V3: the service-worker background model (and the MV2->MV3 lifecycle trap), content-script isolation + message passing, the permissions / host-permissions model and least-privilege posture, storage, the Chrome Web Store / Edge Add-ons / Firefox AMO review pipelines, and the WebExtensions cross-browser delta (Chrome callback vs Firefox browser.* promises). The extension runtime + manifest + store surface — distinct from frontend-engineering (app-grade React UI) and desktop-app-engineering (Electron/Tauri). 3 skills (manifest-permissions-audit, store-submission-readiness), a knowledge bank (MV3 architecture + a permissions-minimization decision tree + a dated cross-browser capability note), best-practices. Security verdicts escalate to security-engineering. Requires ravenclaude-core@>=0.7.0.