Some product ideas aren't sites — they're a button that lives in the browser: clean up this page, track this price, save this to my list. Extensions are a first-class build type here, and they're one of the fastest idea-to-shipped paths on the platform because the stores that carry them review quickly.
Prompting an extension
Say it's an extension and say the moment it acts: "an extension that strips clutter from articles when I click it", "an extension that watches this page for changes and badges the icon". The action moment matters because it decides the shape — a popup, a content script acting on the page, a background watcher — and the builder picks the right one from how you describe the behavior.
What the builder handles that you shouldn't have to know
- The manifest — MV3, the current standard both stores require, with the service-worker background model that implies.
- Permissions, minimal. The build requests only what the behavior needs — over-asking is the number-one store-review trap, and it's also a privacy claim you'd be making by accident.
- The popup/options UI, styled like a product, not a settings dump.
- The icon family at every size the stores demand.
Testing and shipping
The build previews in the chat like any other; the artifact is a store-ready zip you can also load unpacked locally ("developer mode → load unpacked") for a real-browser test. Shipping goes through the store path with your developer accounts — Chrome Web Store with listing autofill, and Firefox Add-ons fully hands-off. The listing kit — screenshots, copy, permission justifications, code-checked privacy answers — generates automatically after the build.