Build a Chrome extension called Signal Crawler using Manifest V3. The extension should help me find business problems in public web pages. It must work on the page I have open, not silently crawl other sites. CORE EXPERIENCE When I click the extension icon, a small animated crawler appears on the page. It moves between readable text blocks, visually scans them and highlights useful passages. A floating panel shows what it has found in real time. Clicking the icon again removes the crawler, panel, highlights and all changes to the page. WHAT TO ANALYZE Support three source types: 1. Job posts: look for manual, repetitive work, slow workflows and tasks that could be automated. 2. Customer reviews: look for repeated complaints, workarounds, missing features and problems that cost the customer time or money. 3. Product and company pages: look for what the business sells, who it serves and how a proposed fix could fit its existing workflow. Ignore navigation, ads, cookie banners, forms, code blocks and hidden text. Handle pages that load more content while scrolling. THE CRAWLER Draw the crawler on a transparent canvas above the page without blocking clicks or text selection. Give it a compact body, eight jointed legs and visible stepping motion. It should move automatically from one relevant text block to another. When it finds a useful passage, pause briefly, place a foot near it, highlight the passage and send a small animated signal from that passage to the floating panel. Use a restrained visual style: warm yellow for findings, white for the body, dark outlines and a subtle glow. Movement should feel quick and alive, but the text must remain readable. SIGNAL BOARD For each finding, show: - the exact quote - the page title and URL - the type of signal - the problem it suggests - how many similar signals have been found Group related findings into clusters. Do not treat one isolated sentence as a proven market. Make repeated evidence visually more prominent than single mentions. ASTRA ANALYSIS Add an optional GPT Astra analysis step. The user enters their own API key and model name in the extension settings. Store the key locally and make API requests from the background service worker, never from the page. For each cluster, ask Astra to produce: - a plain-English description of the problem - who experiences it - evidence for why it matters - the smallest plausible fix - a short draft offer - what still needs human verification Astra must not invent quotes, companies, prices or customer counts. Every conclusion in the panel should link back to its source passages. PANEL CONTROLS Include Pause, Resume, Analyze, Copy Findings, Export JSON, Clear and Close. The panel should show scanning progress, the number of passages checked, findings collected and clusters formed. Let me open any finding and jump back to its original position on the page. QUALITY REQUIREMENTS The extension must not break scrolling, links, page layout or text selection. It should not send messages, contact companies or publish anything automatically. On Close, remove every canvas element, highlight, listener, observer and timer. Support reduced-motion preferences. Handle API failures by keeping the collected evidence visible. Use plain JavaScript, HTML and CSS. Provide every file needed for a working Manifest V3 extension, then give me clear installation and testing steps.
This clip was generated with GPT-6 Astra by OpenAI. The prompt on this page is the exact text used to create it.
The example was generated with GPT-6 Astra using: 36:25 · 0:47 · Animation · Motion Graphics · Advertising. Reusing these settings gives the closest match.
Copy the prompt as-is first, then change the subject while keeping the camera, motion, and lighting terms. Video models are sensitive to wording, so expect a few runs.
Yes. Prompts work best as starting points — swap scenes, adjust pacing terms, or change the aspect ratio to fit your project.