One prompt, many images: why I’m building Berry AI Studio
AI produces multiple images at once, and one prompt can accumulate many variations. I want a better way to revisit, review, and organize those results.
Read note →
DESIGN · CODE · EVERYDAY IDEAS
THE BERRY · Aries
I build tools for writing, creating, and working with AI — making complicated work feel a little more natural.
Based in Shanghai. Curious about how things work, and how they could work better.
I like making tools because a small improvement can change the feel of an entire task. Fewer repeated steps, a file that is easy to find, an idea you can pick up again: these are good reasons to build something. I enjoy following an idea all the way from the interface to the code underneath.
I get particular about the quiet details: whether a save feels certain, whether a shortcut keeps your train of thought, and whether an AI result shows where it came from. Lately, I’ve been exploring calmer writing spaces, ways to revisit creative work, and useful boundaries for agents.
GitHub snapshot · 2026-09-06. Includes 11 forks, plus archived and empty repositories. Repository counts are not shipped-product counts. GitHub ↗
1,517 contributions in the last year
Tools in context — each one connected to work you can explore.
A few questions connecting the things I’m building.
Reading, drafting, and checking syntax need different kinds of focus. I’m interested in making those transitions feel like working on one document, not operating three separate tools.
One prompt can produce many images. I want to make it easier to return to those related attempts, look through the different versions, and keep track of the ones worth continuing.
An agent can gather information and help prepare a quote. Deciding what counts as an official price is a different responsibility. I’m exploring how to make that boundary explicit.
Why these products exist, how I’m shaping them, and the decisions behind the code.
A Markdown workspace for moving between reading, writing, and source without losing the thread of a document.
Read the product story →02A workspace for reviewing and organizing the many image variations produced from the same prompt.
Read the product story →03An agent workspace for costing and quotation, built around traceable inputs and a clear boundary between reference information and official prices.
Read the product story →A few preferences that shape the tools I want to make.
I like ordinary files, understandable exports, and ways to move on without starting over. A tool should be useful enough that you choose to stay.
Saving, switching views, finding something again — these happen all day. I want the interface to make their state clear without repeatedly asking for your attention.
Simple does not have to mean stripped down. Useful power can live one step deeper, ready when you need it, without crowding out the task in front of you.
Open-source collaboration, product design, tool building, or a shared interest — I’m happy to talk. A rough idea, a curious question, or just a hello is a good start.
berrywahlberg@gmail.com