What problem does it solve? Browser extension development fails in predictable ways: service workers that lose state on termination, store rejections from overbroad permissions, CSP violations from runtime template compilation, and untyped messaging that rots the codebase. This Skill encodes the MV3 platform constraints and engineering patterns that survive review and termination. ## Core Features & Use Cases - MV3 Architecture Guidance: Design the ephemeral service worker as an event router, persist state across storage tiers, and handle cold starts with synchronous listener registration. - Security Floor: Apply least-privilege permissions, OAuth with PKCE, sender validation on messages, and strict CSP compliance to pass Chrome Web Store and AMO review. - Tooling and Shipping: Scaffold with WXT, test with Vitest and Playwright persistent contexts, and publish to Chrome, Firefox, and Edge stores via CI. - Use Case: When asked to build a Chrome extension with a popup UI and content script, use this Skill to structure the typed message contract, choose storage quotas correctly, and prepare a store-compliant submission. ## Quick Start Use the browser-extension skill to scaffold a Manifest V3 extension with a typed messaging layer and WXT tooling.