Harry Kanelopoulos

Hi, I'm Harry, the founder of SizeSpec. It launches here on Sunday, November 1.

I built it because every marketplace wants product photos in its own size, shape and file size. Etsy, eBay, Amazon, Shopify, WooCommerce, the App Store and Google Play each have their own rules, and redoing every photo by hand for each one takes forever.

You drop your photos into SizeSpec, pick the marketplace, and get a ZIP with every photo resized, cropped and compressed to that marketplace's rules. The resizing runs in your browser, so those photos are never uploaded.

Most sellers also have a few photos that are just bad: a cluttered desk, dark light. So there is an optional AI tool too. You upload one of your own photos, pick a white background, a styled surface or just better light, and get a cleaner version back in about a minute. That one does send the photo to our AI provider, because the AI has to see it. If you have no photo at all, you can describe the product and generate one.

Opposite of me being someone who translates, I interact with this particular AI in Japanese and everything that is kept also goes in Japanese, i.e., my major rules file with more than a hundred incident notes explaining the basis or reasoning of each rule in general, also, memory notes. I reserve English only for the things that are to be English, such as a forum post or an article in English written by me. It is funny thing though that, with this AI, it tends to speak English quite often with me after long sessions that I was immersed in English documentation. In order to stop it from happening, now, for instance, I set up a trigger where every time this AI answers me in a language which is not Japanese, it will rewrite the English part.

I keep running into this while building with AI: after a few sessions, I end up re-explaining the project, the decisions we made, and what changed.

How do you handle that? Do you keep a project file updated, rely on chat history, or have another system that works?