{"name":"radesjardins-rad-chrome-extension-plugins-rad-chrome-extension","owner":{"name":"ClaudePluginHub"},"plugins":[{"name":"radesjardins-rad-chrome-extension-plugins-rad-chrome-extension","source":{"source":"github","repo":"radorigin-llc/rad-claude-skills"},"description":"MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection, service worker lifecycle, React UI patterns, testing, and Chrome Web Store troubleshooting.\n\nThe chrome-ext-reviewer agent runs two validators before LLM judgment: `audit-manifest.py` (manifest.json audit for MV3 compliance, permission overreach, weak CSP, web_accessible_resources scoping, MV2 leftovers, CWS-rejection causes; auto-discovers WXT `.output/` build manifests) and `scan-mv3-violations.py` (greps source for CSP-banned `eval` / `new Function` / `setTimeout('string')`, remote `<script src=\"http\">` and dynamic imports of remote URLs, MV2-only `chrome.tabs.executeScript` / `chrome.browserAction` / `chrome.extension.getBackgroundPage`, blocking webRequest listeners, optional DOM-risk `innerHTML` / `document.write`). Both emit findings with severity and specific fix recommendations. Pure stdlib Python 3.8+.","version":"1.1.0","strict":true,"keywords":["chrome-extension","manifest-v3","wxt","react","typescript","service-worker","content-script","chrome-web-store","browser-extension","mv3"],"category":"development"}]}