50 Claude Prompts That Build Chrome Extensions
Describe the button your browser is missing and Claude builds it. Every prompt returns the complete extension, each file in full, plus plain install steps. No code, no dev, nothing leaves your browser.
In short: This page contains 50 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Tabs & Focus
9 promptsTab Cleaner that closes what you stopped using
1/50✨ What it does
Claude writes a complete Tab Cleaner Chrome extension that lists every open tab, flags ones you have not touched in days, and closes them after saving the URLs. You follow the install walkthrough, then use it when the tab bar gets out of hand.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Tab Cleaner What it does: Shows every open tab, flags the ones I have not touched in a set number of days, and closes them in one click after saving their URLs. </extension> <requirements> - Popup lists open tabs grouped by how long since I last activated them - A threshold I can set, defaulting to 3 days - A "Save and close" button that copies the URLs into a saved list before closing - A saved list I can reopen later, individually or all at once - Never close a pinned tab, and never close the tab I am currently on </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask for the saved list to export as plain text. It turns the extension into a lightweight read-later system.
Tab limiter that stops you opening the 30th tab
2/50✨ What it does
Claude writes a Tab Limit Chrome extension that caps how many tabs you can open and makes you choose what to close when you hit that number. You set the limit, install it, and keep the escape hatch for the rare time you really need more.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Tab Limit What it does: Enforces a maximum number of open tabs and makes me choose what to close when I hit the limit. </extension> <requirements> - A limit I can set, defaulting to 15 - When I exceed it, show a small overlay listing my oldest tabs and ask which to close - A "just this once" override that raises the limit for 30 minutes - A counter badge on the toolbar icon showing current tab count against the limit </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The 30-minute override is what makes this survivable. Without it most people uninstall by day two.
Focus mode that blocks your own worst sites
3/50✨ What it does
Claude writes a Focus Mode Chrome extension that blocks sites you choose during a timed session and shows a page with how long is left. You add your worst sites, start a session, and sit through it with no subscription or account.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Focus Mode What it does: Blocks a list of sites I choose during a timed focus session, with a blocking page that tells me how long is left. </extension> <requirements> - A site list I manage in the options page - Start a session for 25, 50 or a custom number of minutes - Blocked pages show a clean screen with the time remaining and nothing else clickable - A visible countdown in the toolbar badge - Sessions survive closing and reopening the browser </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask for the block page to show what you said you were working on. Naming the task cuts the urge to override.
Tab search that actually finds the tab
4/50✨ What it does
Claude writes a Tab Finder Chrome extension with keyboard search across every open tab by title and URL, so you can jump without hunting. You install it, then use the shortcut whenever a tab disappears in a crowded window.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Tab Finder What it does: A keyboard-driven search across all open tabs by title and URL, so I can jump to one without hunting. </extension> <requirements> - Opens with a keyboard shortcut - Fuzzy search across tab titles and URLs as I type - Arrow keys to move, Enter to jump to that tab - Shows which window each tab is in - Also searches recently closed tabs and offers to reopen them </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Set the shortcut to something your muscle memory will actually reach for. Most people default to a chord they never press.
Session saver for your working set
5/50✨ What it does
Claude writes a Session Saver Chrome extension that saves a named group of tabs and restores the whole set later. You save a research window before you close it, then reopen that working set next week.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Session Saver What it does: Saves a named group of tabs and restores the whole set later. </extension> <requirements> - Save all tabs in the current window as a named session - A list of saved sessions with tab counts and the date saved - Restore a session into a new window, or add it to the current one - Delete and rename sessions - Export all sessions as a JSON file so I own my data </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Save a session before closing anything. It removes the fear that makes people hoard tabs.
Duplicate tab killer
6/50✨ What it does
Claude writes a Dedupe Tabs Chrome extension that finds tabs open to the same page and closes the extras. You install it and run a cleanup when the same document is open six times.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Dedupe Tabs What it does: Finds tabs open to the same page and closes the extras. </extension> <requirements> - Detects duplicates by URL, with an option to ignore query strings and fragments - Shows what it found before closing anything - Keeps the oldest tab of each duplicate set by default, with a toggle to keep the newest - One-click "close all duplicates" - Never touches pinned tabs </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The ignore-query-strings option matters more than it sounds. Most real duplicates differ by tracking parameters.
Reading timer that shows how long a page will take
7/50✨ What it does
Claude writes a Read Time Chrome extension that estimates how long the current page will take to read before you commit. You glance at the number, then decide to read now or save the page for later.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Read Time What it does: Shows an estimated reading time for the current page before I commit to it. </extension> <requirements> - Calculates from the main article text, not the whole page including navigation and comments - Shows the estimate in the toolbar badge - A reading speed I can adjust in options - Also shows word count on click </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask it to exclude comment sections explicitly, or long comment threads will wreck the estimate.
Auto-grouper that sorts tabs by site
8/50✨ What it does
Claude writes an Auto Group Chrome extension that sorts your tabs into Chrome groups by domain or by rules you set. You turn it on and let the tab bar organize itself instead of dragging tabs around.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Auto Group What it does: Automatically groups my tabs into Chrome tab groups by domain or by rules I set. </extension> <requirements> - Group by domain automatically, with sensible colour assignment - Custom rules, for example all Google Docs tabs into a group called Docs - A manual "group everything now" button - An option to auto-group as new tabs open, or only on demand - Never break existing manual groups </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Start with on-demand grouping. Automatic grouping while you work moves tabs under your cursor and feels hostile.
Snooze a tab until later
9/50✨ What it does
Claude writes a Tab Snooze Chrome extension that closes a tab now and reopens it at a time you choose, such as in an hour or tomorrow morning. You snooze the ones you are not ready to lose, then they come back later.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Tab Snooze What it does: Closes a tab now and reopens it at a time I choose. </extension> <requirements> - Snooze options: in an hour, this evening, tomorrow morning, next week, or a custom time - Snoozed tabs appear in a list with their wake times - Reopens automatically in the background at the chosen time with a notification - Cancel or reschedule a snooze - Survives browser restarts </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Snoozing to "tomorrow morning" is the highest-value option. Ask for it as the default.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Reading & Research
9 promptsPage summariser that works on any article
10/50✨ What it does
Claude writes a Quick Summary Chrome extension that extracts the main article and shows it in a clean panel with the key points. You open the panel on any article and read the summary on your machine, without sending the page away.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Quick Summary What it does: Extracts the main article text from the current page and shows it in a clean reading panel with the key points pulled out. </extension> <requirements> - Strips navigation, ads, sidebars, related-posts blocks, and comment sections - Shows the cleaned article in a readable side panel with adjustable text size - Pulls out the key points as a short bulleted list at the top - A copy button for both the full text and the key points - Works on standard article pages and degrades gracefully when it cannot find an article </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask for the extraction logic to be commented. Sites change layouts and you will want to tweak it.
Highlighter that remembers across visits
11/50✨ What it does
Claude writes a Highlighter Chrome extension that lets you mark text on any page and shows those highlights again when you return. You highlight as you read; the marks stay on your machine with no account.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Highlighter What it does: Lets me highlight text on any page and shows those highlights again when I return. </extension> <requirements> - Select text and highlight it in a colour I choose from four options - Highlights persist per URL and reappear on revisit - A panel listing all my highlights for the current page - Export all highlights for a page as markdown - Delete individual highlights by clicking them </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The markdown export is what makes this useful. Highlights you cannot get out are highlights you never revisit.
Citation grabber for the page you are on
12/50✨ What it does
Claude writes a Cite This Chrome extension that builds a citation for the current page from the title, author, and date it can actually find. You pick the format you need, copy the citation, and fill in any missing details yourself.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Cite This What it does: Generates a clean citation for the current page in the format I need. </extension> <requirements> - Pulls title, author, publication and date from page metadata where available - Formats in APA, MLA, Chicago and plain markdown link - Shows what it could not find rather than inventing it - One-click copy for each format - A note field I can add before copying </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Insist that missing fields are shown as missing. A citation tool that guesses at authors is worse than none.
Research clipper that builds one running document
13/50✨ What it does
Claude writes a Clipper Chrome extension that saves selected text plus its source URL into one growing notes document. You clip as you read, then write from that single attributed file instead of scattered tabs.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Clipper What it does: Saves selected text plus its source URL into a single growing notes document. </extension> <requirements> - Select text, right-click, and send it to my notes with the source URL and date - A panel showing everything clipped, grouped by source - Export the whole thing as markdown with proper source attribution - Search across my clips - Clear all, with a confirmation step </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Attribution on every clip is the point. Unattributed clips become unusable within a week.
Dictionary and context lookup on selection
14/50✨ What it does
Claude writes a Lookup Chrome extension that shows a definition and a plain-language explanation for any word or phrase you select. You select unfamiliar wording as you read and decide whether the explanation is enough.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Lookup What it does: Shows a definition and plain-language explanation for any word or phrase I select. </extension> <requirements> - Select text and a small popup appears near the selection - Shows definition, and for acronyms, what it likely stands for given the page context - A toggle for whether it triggers on selection or only on a keyboard shortcut - Never covers the text I am reading, position it intelligently - Dismiss with Escape or by clicking away </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Make it shortcut-triggered, not selection-triggered. Popups on every selection get infuriating fast.
Paywall-aware read-later that saves the text
15/50✨ What it does
Claude writes a Save Text Chrome extension that stores the readable text of a page on your machine so you still have it if the page changes. You save pages as you go and open the local copy later.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Save Text What it does: Saves the readable text of a page locally so I still have it if the page changes or disappears. </extension> <requirements> - One click saves the extracted article text plus title, URL and date - A library of saved pages with search - Read a saved page in a clean offline view - Export the library as a folder of markdown files - Show storage used, and let me delete individual items </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask for a storage indicator. Local storage has limits and silent failures are confusing.
Compare two pages side by side
16/50✨ What it does
Claude writes a Side by Side Chrome extension that opens two pages in a split view so you can compare them directly. You pick two open tabs, such as two pricing pages or two drafts, and read them together.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Side by Side What it does: Opens two pages in a split view so I can compare them directly. </extension> <requirements> - Pick two open tabs and display them in a split window - Adjustable divider - Synchronised scrolling toggle - Swap sides with one click - Works with any two normal web pages </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Synchronised scrolling only helps on similarly structured pages. Keep it as a toggle, not a default.
Outline generator for long pages
17/50✨ What it does
Claude writes a Page Outline Chrome extension that builds a clickable outline of the current page from its headings. You jump through long docs and reports from the outline instead of scrolling forever.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Page Outline What it does: Builds a clickable outline of the current page from its headings. </extension> <requirements> - Extracts the heading hierarchy into a navigable side panel - Click a heading to jump to it - Highlights which section I am currently in as I scroll - Collapsible nesting - A copy button that copies the outline as markdown </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The "copy outline as markdown" is a quiet win for anyone summarising documents.
Change watcher for a page you care about
18/50✨ What it does
Claude writes a Watch This Page Chrome extension that checks a page on a schedule and tells you when the part you care about changes. You select the region to watch, then wait for the alert instead of refreshing by hand.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Watch This Page What it does: Checks a page periodically and tells me when the part I care about changes. </extension> <requirements> - Select a region of the page to watch - Set how often to check - Notify me when that region changes, showing what was there before and what it is now - A list of watched pages with their last-checked time - Pause or remove any watch </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Watch a specific region, not the whole page. Whole-page watching fires on every ad rotation.
Shopping & Money
8 promptsPrice history tracker on product pages
19/50✨ What it does
Claude writes a Price Watch Chrome extension that records a product price each time you visit and shows whether the current number is actually a good one. You check the history before you believe a sale label.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Price Watch What it does: Records the price of a product page each time I visit and shows me whether the current price is actually a good one. </extension> <requirements> - Detects the price on common shopping pages - Stores price history locally per product URL - Shows a small history panel with the lowest, highest and current price - Tells me plainly whether today's price is high, typical or low against what I have seen - Manual price entry as a fallback when detection fails </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Manual entry as a fallback matters. Price detection breaks constantly as sites change markup.
Unit price calculator for supermarket pages
20/50✨ What it does
Claude writes a Unit Price Chrome extension that shows the price per unit on shopping pages so you can compare sizes honestly. You glance at the per-unit number and pick the pack that is actually cheaper.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Unit Price What it does: Shows the price per unit on shopping pages so I can compare sizes honestly. </extension> <requirements> - Detect price and quantity, then display price per kilogram, litre or unit - Show it directly next to the listed price - Handle multipacks correctly - A manual override when detection is wrong - Works on listing pages, not just individual product pages </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Multipack handling is where these always break. Call it out explicitly in the prompt.
Subscription spotter in your inbox tabs
21/50✨ What it does
Claude writes a Subscription Spotter Chrome extension that flags recurring-payment language on checkout and pricing pages before you sign up. You read the flag, then decide if the trial or plan is worth the renewal.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Subscription Spotter What it does: Flags recurring-payment language on checkout and pricing pages before I sign up. </extension> <requirements> - Detects trial lengths, auto-renewal terms, and cancellation conditions in page text - Shows a clear summary badge: what I will be charged, when, and how often - Highlights the actual cancellation terms if the page contains them - Warns when a free trial converts to paid automatically - Never blocks the page, only informs </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask it to quote the exact sentence it found. A summary you cannot verify is not much use at checkout.
Currency converter that works inline
22/50✨ What it does
Claude writes an Inline Currency Chrome extension that converts prices on the page into your home currency. You select a price or turn it on for the whole page, then shop without doing the math in your head.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Inline Currency What it does: Converts prices on the page into my home currency. </extension> <requirements> - Select a price and see the converted amount, or convert all detected prices on the page - A home currency I set once in options - Let me enter and store my own exchange rate rather than calling an external service - Show the rate used and when I last updated it - Round sensibly and never imply more precision than the rate justifies </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: A stored manual rate keeps it fully local. Ask for a visible "rate last updated" so you notice when it is stale.
Cart total sanity check
23/50✨ What it does
Claude writes a Cart Check Chrome extension that shows what your cart will actually cost, including extras that appear at the last step. You look at the full total before you confirm the order.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Cart Check What it does: Shows what my cart will actually cost including the extras that appear at the last step. </extension> <requirements> - Detect the subtotal on cart pages - Let me enter typical shipping, tax and fee percentages once - Show the realistic total up front - Flag when the final checkout total differs from my estimate, and by how much - Keep a simple log of recent estimated versus actual totals </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The estimate-versus-actual log quietly teaches you which retailers add the most at the end.
Wishlist that lives in your browser
24/50✨ What it does
Claude writes a Wishlist Chrome extension that saves products you are considering with the price at the moment you saved them. You add items from any site, then check later whether the price has moved.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Wishlist What it does: Saves products I am considering with their price at the time I saved them. </extension> <requirements> - Save the current product page with title, price, image and URL - A grid view of everything saved with the saved price and today's price where detectable - Mark items as bought or remove them - Sort by date added or price change - Export as a plain list </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The price-since-saved column is the feature. It converts browsing into a waiting game you can win.
Discount code field checker
25/50✨ What it does
Claude writes a Code Check Chrome extension that keeps your own list of discount codes and reminds you to try them at checkout. You add codes you already have; nothing gets swapped for an affiliate link.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Code Check What it does: Keeps my own list of discount codes and reminds me to try them at checkout. </extension> <requirements> - A personal list of codes I add manually with the retailer and any expiry - On a checkout page for a matching retailer, show my saved codes - Mark codes as worked or failed so I stop retrying dead ones - No scraping and no external code sources, this is only my own list - Sort by most recently worked </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Keeping it to your own codes is the point. Coupon extensions that fetch codes usually rewrite affiliate links.
Spending pause button
26/50✨ What it does
Claude writes a Cooling Off Chrome extension that adds a delay between deciding to buy and buying, and keeps a record when you skip the wait. You list the retailers, sit through the pause, and notice how often you override it.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Cooling Off What it does: Adds a deliberate delay between deciding to buy and buying. </extension> <requirements> - On checkout pages at retailers I list, show an overlay asking me to wait - A configurable delay, defaulting to 24 hours, per item - A list of items currently cooling off with the time remaining - An override that requires typing a reason, which is then saved to a log - Show my override log so I can see my own patterns </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The typed-reason override is what makes it work. The log becomes uncomfortable reading, which is the point.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Work & Automation
8 promptsOne-click meeting notes template
27/50✨ What it does
Claude writes a Meeting Notes Chrome extension that drops a structured notes template into any text field with one click. You edit the template once, then paste it into the doc or chat where you take notes.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Meeting Notes What it does: Drops a structured meeting-notes template into any text field with one click. </extension> <requirements> - A template I define in options with placeholders for date, attendees, decisions, and actions - Insert it into whatever text field is focused - Auto-fill today's date - Multiple named templates I can pick between - A keyboard shortcut for the template I use most </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Keep the template short. Long templates get abandoned mid-meeting.
Text expander for the phrases you retype
28/50✨ What it does
Claude writes an Expander Chrome extension that turns short abbreviations into full text as you type, anywhere in the browser. You add the phrases you retype, then let the shortcuts expand while you work.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Expander What it does: Expands short abbreviations into full text as I type, anywhere in the browser. </extension> <requirements> - Define abbreviation and expansion pairs in options - Trigger on typing the abbreviation followed by a set character - Work in normal inputs, textareas, and standard rich-text editors - Support a cursor-position marker so I can define where the caret lands - Import and export my snippet list </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The cursor-position marker is what separates a useful expander from an annoying one. Do not skip it.
Form filler for the fields you always fill
29/50✨ What it does
Claude writes a Form Fill Chrome extension that fills repetitive fields from a saved profile on command, and it refuses to touch passwords. You store your common details locally, then trigger a fill on the next form.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Form Fill What it does: Fills repetitive form fields with my saved details on command. </extension> <requirements> - A saved profile of my common details, stored locally only - A keyboard shortcut that fills matching fields on the current form - Show me what it filled and let me undo - Never auto-fill without an explicit command - Never store passwords or payment details, and say so clearly in the options page </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The explicit refusal to store passwords is a feature. Build it that way and you never have to worry about the storage.
Screenshot with annotation, saved locally
30/50✨ What it does
Claude writes a Snap Chrome extension that captures a region of the page and lets you annotate it before saving. You draw the boxes and arrows, then save the image on your machine with no cloud upload.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Snap What it does: Captures a region of the page and lets me annotate it before saving. </extension> <requirements> - Select a region to capture - Draw boxes, arrows and add text on the capture - A blur tool for hiding sensitive information - Save as PNG or copy to clipboard - Everything happens locally with no upload </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The blur tool is the one people miss until they have shared a screenshot with a customer name in it.
Quick link shortener using your own rules
31/50✨ What it does
Claude writes a Tidy Link Chrome extension that strips tracking parameters from URLs before you share them. You copy the cleaned link and send that instead of the long tracked one.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Tidy Link What it does: Strips tracking parameters from URLs before I share them. </extension> <requirements> - Remove common tracking parameters from the current URL - Show the before and after so I can see what was removed - A custom list of parameters to strip that I can edit - One-click copy of the cleaned URL - Also clean any URL I paste into its input box </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Ask for the before-and-after view. Some parameters are load-bearing and you need to spot when one gets stripped.
Timer that logs where your hours went
32/50✨ What it does
Claude writes a Time Log Chrome extension that starts a timer against a task you name and keeps a private log of where the hours went. You start and stop it yourself; no account and no employer can see it.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Time Log What it does: Tracks time against a task I name, and logs it. </extension> <requirements> - Start a timer with a task name and optional project - A visible running timer in the toolbar badge - Stop and log, with the entry saved locally - A log view grouped by day and project with totals - Export the log as CSV </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Manual start beats automatic tracking here. Automatic trackers record activity, not work.
Clipboard history you can search
33/50✨ What it does
Claude writes a Clip History Chrome extension that keeps a searchable history of text you copied in the browser. You search the last fifty items when you need the thing you copied three copies ago.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Clip History What it does: Keeps a searchable history of what I have copied in the browser. </extension> <requirements> - Store the last 50 copied text items locally - Search across them - Click any item to copy it again - Pin items so they never get pushed out - A clear-all button and an option to exclude specific sites entirely </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The site exclusion list matters. Exclude your password manager and banking sites explicitly.
Do-not-disturb for browser notifications
34/50✨ What it does
Claude writes a Quiet Hours Chrome extension that suppresses web notifications during hours you set, by day of the week. You pick the windows, then keep notifications off without turning them off forever.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Quiet Hours What it does: Suppresses web notifications during hours I set. </extension> <requirements> - Set quiet-hours windows per day of the week - Suppress notifications from sites during those windows - A queue showing what was suppressed, viewable afterwards - A per-site allowlist for genuinely urgent sources - Manual toggle for an immediate quiet period </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The suppressed-notification queue is what makes this safe to leave on. Nothing is lost, just delayed.
Privacy & Cleanup
8 promptsCookie banner auto-dismisser on your terms
35/50✨ What it does
Claude writes a Banner Away Chrome extension that dismisses cookie consent banners by picking the most private option it can find. You install it and let it choose reject-all on the banners you used to hunt through.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Banner Away What it does: Dismisses cookie consent banners by selecting the most private available option. </extension> <requirements> - Detect common consent banners - Choose reject-all or essential-only where that option exists - Where only accept exists, hide the banner without consenting and tell me it did so - A per-site disable list for sites where it interferes - A counter showing how many it has handled </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The "hid it without consenting" distinction matters. You want to know when it could not actually reject.
Autoplay blocker with per-site memory
36/50✨ What it does
Claude writes a No Autoplay Chrome extension that stops video and audio from starting on their own, with a per-site allow list. You leave it on, then allow the few sites where you actually want sound.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: No Autoplay What it does: Stops video and audio from playing automatically. </extension> <requirements> - Block autoplaying media on page load - A per-site allowlist for sites where I want autoplay - A visible indicator when something was blocked, with a click-to-play button - Do not break media I actively started - A global on-off toggle </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The click-to-play indicator is essential. Silent blocking makes video sites look broken.
Site data cleaner you can point at one domain
37/50✨ What it does
Claude writes a Clean Site Chrome extension that clears cookies and local storage for the current site only. You hit the button on one domain instead of wiping your whole browser.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Clean Site What it does: Clears cookies and local storage for the current site only. </extension> <requirements> - One button clearing cookies, local storage and session storage for the current domain - Show what will be cleared before doing it - A protected list of sites it will never clear, for the ones I stay logged into - A log of recent cleans - An option to also reload the page afterwards </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Set the protected list before first use. Otherwise you will log yourself out of something important.
Element hider for the parts of a site you hate
38/50✨ What it does
Claude writes a Hide That Chrome extension that lets you permanently hide any element on a page, such as a sticky header or recommended bar. You click the thing you resent, then it stays gone on later visits.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Hide That What it does: Lets me permanently hide any element on a page. </extension> <requirements> - Click an element to select it, with a visual outline as I hover - Hide it, and remember it for future visits to that site - A list of hidden elements per site, with the ability to unhide - An option to hide by element type across a whole site - A global toggle to temporarily show everything again </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The temporary show-everything toggle saves you when a hidden element turns out to be load-bearing.
Referrer and history minimiser
39/50✨ What it does
Claude writes a Quiet Browsing Chrome extension that strips referrer details on outbound links so sites learn less about where you came from. You turn it on and browse with that modest privacy gain, without expecting invisibility.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Quiet Browsing What it does: Reduces what sites learn about where I came from. </extension> <requirements> - Strip referrer information on outbound links from sites I list - Show an indicator when it is active on a page - A per-site configuration - Explain in the options page exactly what this does and does not protect against - No claims of anonymity, be honest about the limits </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Insist on the honesty requirement. Privacy tools that overstate protection are actively harmful.
Download organiser by source site
40/50✨ What it does
Claude writes a Sort Downloads Chrome extension that renames and files downloads based on the site they came from. You keep using the browser as usual, then find files by source months later.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Sort Downloads What it does: Renames and organises downloads based on where they came from. </extension> <requirements> - Prefix downloaded filenames with the source domain and date - A rule list mapping sites to filename patterns - Preview the resulting filename before the download completes where possible - A log of recent downloads with their original and new names - A per-site disable option </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: Date-prefixing alone solves most of the problem. Start there before building complex rules.
Permission auditor for sites you have granted access
41/50✨ What it does
Claude writes a Permission Audit Chrome extension that lists which sites have camera, microphone, location, and notification access. You review the list and revoke the ones you granted once and forgot.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Permission Audit What it does: Shows me which sites have camera, microphone, location and notification permissions. </extension> <requirements> - List all sites with granted permissions, grouped by permission type - Show when each was granted where that information is available - Revoke any permission from the list - Flag permissions I have not used recently - A plain-language explanation of what each permission actually allows </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The "not used recently" flag is the useful column. Most stale permissions are ones you granted for a single task.
Login session lister
42/50✨ What it does
Claude writes a Where Am I Logged In Chrome extension that lists domains with an active session cookie on this machine. You scan the list and sign out of the ones you no longer want open.
<context> I want a working Chrome extension and I do not write code. Build the complete thing, then walk me through installing it. </context> <extension> Name: Where Am I Logged In What it does: Shows which sites I currently have an active session with. </extension> <requirements> - List domains with session cookies present - Group by how recently I visited - One-click clear session for any listed site - A protected list that it will never touch - Explain clearly that this reflects local cookies, not server-side sessions </requirements> <deliverables> Give me every file in full, ready to paste, with the filename above each one: - manifest.json using Manifest V3 - every HTML, CSS and JavaScript file needed - a note on which permissions you requested and exactly why each one is needed Then give me numbered install steps for chrome://extensions with Developer Mode, written for someone who has never done this. </deliverables> <constraints> - Manifest V3 only. No deprecated V2 APIs. - Request the minimum permissions that make it work. If a feature would need a scary permission, tell me and offer a narrower alternative. - Everything runs locally. No external servers, no analytics, no data leaving my browser. - Clean, readable interface. Assume I will want to change the colours later, so keep styling in one obvious place. - Add short comments explaining anything I would plausibly want to edit. </constraints> <after> Once it works, suggest three small upgrades I could ask you for next, ordered by how much they would improve daily use. </after>
Pro tip: The honesty note about server-side sessions matters. Clearing a cookie is not the same as logging out everywhere.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides