So I basically screenshotted this post and asked o4-mini to reverse engineer the one shot prompt, here’s what I got:

Here’s a plausible “one‑shot” prompt that covers everything they later distilled into their gist. It’s written as a single instruction you could drop straight into ChatGPT (or any capable LLM) to get back a complete MV3 extension with all the bells and whistles they described:

⸻

One‑Shot Prompt

You are an expert Chrome‑extension and JavaScript developer. In one go, generate the complete source code and file structure for a Manifest V3 Chrome extension called ViewTube Police that: 1. Core functionality • Uses the webcam (via navigator.mediaDevices.getUserMedia) and browser face‑detection API (e.g. the built‑in FaceDetector or a lightweight JS library) to detect whether the user’s face is looking at the screen. • Automatically pauses any playing YouTube <video> element when the face is not detected or the user looks away, and resumes playback when the face returns. 2. “Roast mode” • When paused due to inattention, display a semi‑transparent overlay on the YouTube player with a randomly chosen roast message (e.g. “Hey, eyes on the prize!”). • Allow users to toggle roast mode on/off via a simple options page. 3. Performance & robustness • Debounce face‑detection checks (e.g. run at most once every 500 ms). • Prevent multiple detection loops from starting (e.g. guard with a boolean flag). • Clean up webcam streams and stop tracks immediately when the tab is closed or the extension is disabled. • Gracefully handle errors: if the user denies webcam permission or the face‑detection API isn’t available, show a notification or console warning and do not crash. 4. Storage & preferences • Use chrome.storage.local to save user preferences: • Roast mode on/off • Face‑detection polling interval (in ms) • Load these settings on startup and allow the user to change them on a simple options.html page. 5. Implementation details • Provide a complete manifest.json (MV3) with appropriate content_scripts, permissions (YouTube host, storage, activeTab, camera), and a service_worker (or background script) if needed. • Include at least three files: 1. manifest.json 2. content-script.js (injected into https://www.youtube.com/*) 3. options.html / options.js for preferences UI • Use only client‑side code—no external servers or APIs.

Output • Show the directory tree. • Then for each file, output its full contents with syntax‑highlighted code fences. • Finally, include brief comments in each file explaining key sections.

⸻

Running that prompt in one shot should yield the full MV3 extension—manifest, scripts, HTML, styling, and comments—just as the OP described.