moai-platform-chrome-extension

Creates modular, action-oriented guidance for building MV3 Chrome extensions.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/windysky/snake-game --skill moai-platform-chrome-extension-windysky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-platform-chrome-extension
Source: https://github.com/windysky/snake-game/tree/main/.claude/skills/moai-platform-chrome-extension
Command: npx skills add https://github.com/windysky/snake-game --skill moai-platform-chrome-extension-windysky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a comprehensive MoAI-based blueprint and reference framework to help developers build, migrate, and publish Chrome extensions using Manifest V3, covering core concepts like service workers, content scripts, messaging, UI patterns, and security considerations.

Core Features & Use Cases

  • Modular, action-oriented guidance for MV3 extension development across core areas (service workers, content scripts, messaging, UI components, and security).
  • Reusable references and templates that accelerate migration from MV2 to MV3 and ensure CSP compliance and publishing readiness.
  • Real-world use cases including building, auditing, testing, and publishing Chrome extensions for the Web Store.

Quick Start

Create a complete MV3 Chrome extension scaffold using MoAI patterns and reference modules.

Frequently Asked Questions about moai-platform-chrome-extension

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Chrome extension from MV2 to MV3?

To migrate a Chrome extension from MV2 to MV3, you must replace background pages with service workers, update manifest.json fields, and ensure CSP compliance. This framework provides reusable templates and guidance to audit and complete the MV2 to MV3 migration.

How does the service worker lifecycle work in Manifest V3 extensions?

The service worker lifecycle in Manifest V3 extensions is event-driven, terminating when idle and restarting on new events. This blueprint guides managing this lifecycle, registering listeners, and handling state persistence correctly in your service worker.

What is the best way to set up messaging between content scripts and service workers?

The best way to set up messaging between content scripts and service workers is using the chrome.runtime API for cross-context communication. This reference provides action-oriented patterns to structure secure messaging pipelines between your extension components.

How do I pass Content Security Policy (CSP) checks when publishing a Chrome extension?

To pass Content Security Policy (CSP) checks when publishing a Chrome extension, you must configure manifest.json correctly and remove inline scripts. This framework provides auditing steps to ensure CSP compliance and Web Store publishing readiness.

Can I use this to scaffold a complete MV3 Chrome extension with UI components?

Yes, you can scaffold a complete MV3 Chrome extension with UI components using this framework. It offers a quick start approach to generate modular structures covering manifest.json, service workers, content scripts, and UI patterns.