--- name: "chrome-web" description: "Chrome extensions (MV3, chrome.*/browser.* APIs, side panel, content/user scripts, Web Store publishing) and modern web platform (Baseline, CSS/JS APIs, Core Web Vitals, built-in AI). Checks live developer.chrome.com and web.dev via Google Developer MCP." license: Complete terms in LICENSE.txt --- # Chrome extensions + web platform Google's browser side, next to `android-compose`. Visual direction and UX → design plugin / `frontend-design`. Hosting → `cloudflare`. ## Live docs first APIs move every Chrome release (4 weeks). Everything below is a trap list, not a spec. | Source | Use for | |---|---| | **Google Developer MCP** `search_documents` → `get_documents` | developer.chrome.com (extensions API reference, manifest keys, **What's new in extensions**, Web Store policy) and web.dev (guides, Baseline, CWV). `answer_query` = synthesized, low quota | | `npx -y modern-web-guidance@latest search ""` → `retrieve ` | Google's curated web-platform guides (dialogs, popovers, anchor positioning, view transitions, forms/autofill, passkeys, INP/LCP, built-in AI) with Baseline fallbacks. Claude Code / any shell with network and approval. Chat default stays the MCP | | MDN / caniuse (WebFetch) | Per-browser compat when the user targets Safari/Firefox too | Unsure after 1-2 searches → say "not in official docs", don't invent. Cite the doc page. ## Extensions: hard rules - **MV3 only.** `background.service_worker`, `chrome.action`, `chrome.scripting`, `host_permissions` separate, no remote code, no inline `