Blog / Build with AI /
Extension ideas for productivity
Once you have built your first Chrome extension, the next question is always the same: what do I build now?
The best answer is almost boring. Build the extension for the thing that annoys you most often. Productivity tools are good for this because the annoyances are daily, easy to describe and quick to test.
Here are fifteen ideas, sorted by how hard they are. If you have not made one yet, start with your first Chrome extension, then come back.
How to pick
Ask three questions of any idea:
- Will I use it this week? If not, it is a toy.
- Can it do one thing? Extensions with five jobs usually do none well.
- Can it work without sending page data anywhere? The more local, the simpler and safer.
An extension that reads pages deserves care. Request the fewest permissions you can.
Easy: one script, no settings
These can be a manifest file and a short content script.
1. Reading time badge. Shows an estimated reading time on articles. It is the example from the first-extension post.
2. Link opener fix. Makes every external link open in a new tab, or the opposite. Good for sites that behave badly.
3. Highlight my keywords. Highlights a short list of words on any page, handy when you scan long documents.
4. Hide the clutter. Removes a specific element on a site you use daily, such as a sidebar, a suggested videos list or a cookie banner that appears every visit. Use it only on sites where you are certain that is allowed and harmless.
5. Always-visible date. Many pages bury the published date. A script can look for it in the page’s structured data and show it in a corner. This is handy for judging whether advice is old.
Medium: a popup and a little storage
These need a small interface that opens when you click the toolbar icon.
6. One-click notes. A tiny text area saved in the browser. Jot down a thought without opening another app.
7. Copy page as a link. Copies the title and URL as a ready-made Markdown link or HTML anchor. If you write posts, this saves seconds hundreds of times.
8. Focus timer. A 25-minute countdown with a badge showing the remaining time. It is a proper chance to learn about timers and notifications.
9. Tab snapshot. Saves the list of open tab titles and URLs to a text file or clipboard so you can recover a working session.
10. Clean URL copier. Strips tracking parameters such as utm_ from the current address before copying. Web admins use this constantly; it is also a decent introduction to working with URLs in code.
Harder: settings, rules and care
These involve more moving parts, and more ways to go wrong.
11. Site-specific shortcuts. Keyboard shortcuts that click particular buttons on a tool you use all day, such as a dashboard. It involves reading the page structure, which can change without warning.
12. Page checker for your own sites. A popup showing the title length, meta description, heading structure and whether the page is set to noindex. It reads the page you are on and shows a summary. It is a good project for anyone who audits sites.
13. Snippet expander. Type a short code like ;sig and have it expanded to a saved block of text. Useful, but you have to handle text fields carefully so it does not interfere with typing.
14. Daily site status board. A popup listing a few of your sites and whether they respond. This needs network requests, so permissions matter. Monitoring a website with an automated check covers the thinking.
15. Tab organiser. Groups or colour-labels tabs by rule. Tab management has been tried many times, which means you will learn quickly what the tricky parts are. It is a rich project but not a first one.
Turning an idea into a prompt
Take idea 7, the link copier. A solid prompt reads:
Build a Chrome extension using Manifest V3. When I click the toolbar icon, a small popup shows two buttons: “Copy Markdown link” and “Copy HTML link”. Each copies the current page’s title and URL in that format to the clipboard and shows “Copied” for two seconds. Request only the permissions needed. Provide all files and explain how to load it.
Notice the structure: platform, trigger, exact outputs, behaviour, constraint on permissions, and a request for loading instructions. It gives the assistant very little room to wander.
Common problems
- Too many permissions. If the assistant requests access to all sites and your history for a clipboard tool, push back.
- Old tutorials baked in. Make sure you get Manifest V3.
- Clipboard rules. Browsers restrict clipboard access to user actions, so something that copies silently on page load will not work.
- Page layouts change. Anything that targets a specific site’s elements breaks when that site updates. Expect to maintain it.
- Feature creep. Finish the single job before adding a settings page.
Before you share one
An extension that works on your machine is not ready for other people. Try it on several sites, in a fresh browser profile and with your other extensions off. Think about what it reads and whether you would be comfortable explaining that to a stranger. Extension analytics without spying on users is worth reading if you plan to measure usage.
For people who run websites
Several ideas here exist because site work is full of tiny repeated steps: checking a title, copying a clean URL, spotting a noindex tag, confirming a page is up. If you do any of those daily, an extension turns a minute into a click. That is the kind of productivity that pays off without any grand plan.
Key takeaways
- Build for a daily annoyance you will use this week.
- One job per extension, and as little page access as possible.
- Start with a single script, then add a popup and storage.
- Give the assistant a precise prompt: platform, trigger, outputs, permissions.
- Test on several sites before sharing.
Related reading
- Extension ideas for online shoppers
- Your first Chrome extension: a ten-line example
- Choosing your first AI project: small, useful and finishable
Which of the fifteen would you actually use tomorrow morning?