One conversationInteractive, not one literal prompt
6–12 NovemberBuild, refine, sign, publish
A public resultFirefox add-on 1.0.0
From wish to something shareable
6 Nov
Start with the page, not a platform.
The request was to put real Google reviews beside each restaurant on the live e-food list. The agent inspected the page and discovered its existing Google Places library. No new review backend or developer-owned API key was needed.
6 Nov
Make the first thing work.
The first working review panel was reported about three minutes after the request. Live checks then caught a wrong branch of a restaurant chain. Reading the restaurant’s own page supplied the branch information needed for a better match.
6–8 Nov
Make it something a person can install.
“It has to work on Mozilla too.” A userscript was not the final answer: extra installation tools were rejected. The same conversation produced a standalone Firefox extension, its package, icons, listing and privacy text.
8 Nov
Less code. Less guessing.
A request for less code cut an approximately 25.9 KB script to 10.4 KB. Actual visual feedback fixed awkward chips and navigation behaviour. A further correction replaced case-by-case patches with structural card discovery and general name-and-branch ranking.
9–10 Nov
Carry it through the unglamorous part.
Mozilla validation required a manifest correction. The owner handled account sign-in and two-factor authentication; the agent handled packaging and submission. A signed self-distribution release came first. Review took longer than the agent initially promised.
12 Nov
A real public destination.
The public Firefox listing became available. The published signed file was downloaded and checked, and its extension loaded in a clean Firefox Developer Edition profile without disabling signature checks. The work could now leave the development conversation.