Results for “chrome-extension”

Build cross-browser extensions with WXT — the modern framework for Chrome, Firefox, Safari, and Edge extensions. Use when someone asks to "build a browser extension", "Chrome extension with React", "WXT framework", "cross- browser extension", "manifest v3 extension", "build Firefox extension", or "browser extension with TypeScript". Covers content scripts, background workers, popup/options pages, storage, messaging, and publishing.

Controls a Chrome browser through the AIPex extension and MCP bridge, enabling navigation, clicking, form filling, screenshots, tab management, and content downloads.

Fetches any URL via Chrome CDP and converts HTML to clean markdown, supporting auto-capture and wait-for-user modes for login-required pages.

Turns websites into CLI commands, reusing an existing Chrome login session for browser-backed data extraction and structured output.

Exports cookies from a local Chrome browser and saves them into a Browserbase persistent context, enabling authenticated browsing sessions via the browse CLI.

Controls and inspects a live Chrome browser for automation, debugging, and performance profiling using the Chrome DevTools MCP server.

Deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments using the Adobe I/O CLI plugin.

Connect to an existing Chrome browser via Chrome DevTools Protocol to navigate, click, type, screenshot, evaluate JavaScript, read the accessibility tree, and monitor console or network events.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

Fetch any URL and convert it to clean markdown using a Chrome CDP-based CLI with site-specific adapters for X/Twitter, YouTube, Hacker News, and generic pages.

Browser-automates Google's NotebookLM to read notebooks, add sources, generate Studio outputs (Audio/Video Overviews, Mind Maps, Reports), and create new notebooks.

Build and maintain Raycast extensions using the Raycast API, covering UI components, data persistence, feedback, and restricted APIs like AI and Browser Extension.

Use Expo DOM components to run web code in a webview on native and as-is on web, enabling incremental migration of web code to native.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.

Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, React patterns, Vue patterns, Nuxt patterns, Astro patterns, TanStack Start patterns, Expo patterns, React Router patterns, Chrome Extension patterns, organizations, billing, subscriptions, payments, pricing, plans, seat-based pricing, feature entitlements, syncing users, or testing. Automatically routes to the specific skill based on their task.

Use when the user wants to clone or adapt a UI pattern from any website into gotcontext.ai, or asks to "build something like X", "make our nav look like Y", or "clone that component". Prefer aura.build Pro when available; without a Pro subscription, skip Aura and go straight to Phase 2.5 direct rebuild. Aura's clone is now NATIVE — paste a URL or drag a screenshot into aura.build and it generates React/Tailwind directly; the Anima/Chrome-extension flow is only a fallback for login-gated pages Aura can't fetch server-side.