moai-platform-chrome-extension

To build a Chrome extension with Manifest V3, you configure a service worker for background logic, define content scripts, and declare permissions in the manifest. This Skill provides reference guidance for setting up the project structure and implementing core extension lifecycle management.

In Chrome extensions, a service worker runs in the background to handle browser events and chrome.* APIs, while content scripts inject directly into web pages to read or modify DOM content. This Skill explains how to configure both and establish secure message passing between them.

You use declarativeNetRequest in a Manifest V3 extension to define static rules that block or modify network requests without requiring persistent background scripts. This Skill covers implementing declarativeNetRequest rules to block distracting websites and manage user preferences via storage.

Manifest V3 supports side panels and secure message passing between background service workers, content scripts, and popup interfaces. This Skill details how to implement side panels and establish secure communication channels using modern Chrome APIs and security best practices.

Manifest V3 service workers are ephemeral and terminate when idle, unlike persistent background pages, which affects long-running tasks and state management. This Skill addresses these limitations by covering service worker configuration, lifecycle management, and secure state persistence via chrome.storage.

To publish a Chrome extension to the Chrome Web Store, you must package your Manifest V3 project, configure content security policy, and manage required permissions correctly. This Skill provides guidance on Chrome Web Store deployment and security best practices for successful publishing.