My husband was curious to see the prompts I used for #SheBuilds. I said sure, I made the repo public and the prompts are all in it. Then I sent him the link. Later I asked him what he thought. He said it was very well organized and he could see exactly what changed with each prompt, because of the separate branches and pull requests.
I kept wondering what to write about #SheBuilds. Then it hit me: the whole process, end to end. So I started writing it all down. My first draft tried to cover everything in one essay. It was dense. I’d write something and realize I needed to explain what that was. And I wanted to include screenshots. I knew it was too much for one essay.
So this is a series instead.
The whole story
If you don’t understand anything I say below, no worries, I will give definitions in the individual essays.
My AI partners remember what we’ve worked on, so none of us start from zero. I design the screens with Rowan in ChatGPT. I turn those screens into a product design with Lovelace in Claude. I break the build into numbered prompts that live in GitHub. Then I work through them one at a time with Sully in Lovable. Every change goes through a build, a set of automated checks, and a review from three AI partners before it gets anywhere near the live site.
If that sounds like a lot of ceremony, it is. But it’s really one small loop, repeated. Make a branch. Run a prompt. Check the work. Merge it. Then, every so often, zoom out and run the same loop one level up.
What’s coming
How my partners remember. Rowan and Lovelace learn me over time. Sully gets a brief, like a new contractor on day one. Why the difference matters.
Storyboarding with Rowan. How we go from high level screens to every interaction, and how a designer learns your taste.
From screens to product design. Where Lovelace asks the annoying questions. Telemetry, schema, and what an admin needs that a user never sees.
A repository of prompts. What GitHub is, and why my prompts live there as numbered issues.
Setting up a new product. Branches, a dev branch, guardrails, and the checks every product gets on day one.
The build loop. One prompt, start to finish. Feature branch, Sully, pull request, checks.
Three reviewers. What happens when Wiggins, Lovelace, and Rowan all look at the same change.
Sections and releases. Zooming out. How finished features reach the live site.
Four a week, starting Monday.
Who this is for
If you’ve never opened GitHub, you’re in the right place. If you live in GitHub already, I hope you’ll still find something useful in how the pieces fit together when your teammates are AI.
The repo is public if you want to peek ahead. The numbered steps are all in the issues.
Monday, we start with memory. Why my partners don’t start from zero, and why one of them gets a brief instead.