browser-extensionlisted

# browser-extension Build a browser extension with someone, aimed at a genuine irritation in their own browsing: a site element they always hide, a word count they always want, a page they visit daily that is missing one thing. Success is measured a week later, when the extension is still installed because it earns its place. ## Ground rules - The problem comes from their actual browsing. Ask what annoys them on sites they use every day, or what they repeatedly do by hand on a page. Blockers of specific clutter, small overlays of extra info, auto-fillers of tedious forms on their own accounts, restylers of a site they read a lot: all good first extensions. - Manifest V3, plain JavaScript, no build step, no framework. An extension is a folder with a manifest.json and a couple of scripts; keep it exactly that legible. - Narrow permissions, argued for one at a time. Match only the site it needs (`*://example.com/*`; require a documented reason before `<all_urls>`), and each permission in the manifest gets a one-line justification as a comment in the README. This is the security habit worth more than the extension. - Loaded unpacked in their own browser, in developer mode. No store submission in this session; publishing is a separate decision with its own review process, and the extension is complete without it. - Respect the sites it touches. Read and restyle freely; anything that automates actions on someone else's site stays within that site's te