Summary
Georgia Jean sits in on a call or a solo brainstorm. She listens, flags tension, gives feedback when you ask, and writes a build prompt as you talk, so you leave with something Claude Code can build. I founded, designed and built her.


Role
Founder, designer and builder
Team
Solo
Timeline
April to October 2026
Tools
Figma, Claude Code
Part 01
The problem
Talking and building happen on different days.
You brainstorm the idea on a call.
After everyone hangs up, someone turns it into a plan.
The building happens on another day.
Claude Code builds a prototype in minutes. Turning a conversation into instructions is the slow part. Georgia Jean does it while you talk.
What it looks like now
She listens, and the build prompt underneath keeps updating as decisions are made.
Under the hood
Every AI service sits behind a login.
Part 02
The problem
She is in the session for its whole length, doing something different minute to minute. A spinner in one corner can't say that, so her state is shown on her.

Listening. Her eyes stay closed and she nods along, faster while someone is talking.

Thinking. She looks up with her head tilted, and a thought cloud appears while Claude works.
Answers

The build prompt

Part 03
By default
In a live call, an AI that keeps talking competes with the people in it. So feedback is always on demand: one tap on a button under her.
The one exception

Part 04
How she writes for Claude
Claude Code works best with component names, files, state and design tokens. She writes the conversation up in that language, in two sections, the whole time you talk.
From one of my sessions
## Design Changes Feedback expands an inline row below the three buttons: Ideas, Questions, Concerns, Summary. Accordion reveal, no new page. ## Code Changes MeetingHub: const [feedbackOpen, setFeedbackOpen] = useState(false) Map sub-options to buildIdeas(), buildQuestions(), buildConcerns() Tokens: remove purple, add --color-primary: #1E3A8A
Two sections, every timeDesign Changes for components, layout and copy. Code Changes for files, logic, APIs and data.
Always the latestRewritten from the whole conversation, so when a decision flips, the old one is gone.
The button says "Copy for Claude". It used to say "Send to Claude Code", which promised something it didn't do.
Part 05
How she hears the call
I also replaced the browser's built-in speech recognition, which stalled and misheard, with Deepgram streaming, which labels who is speaking.
The first question

The session screen
Her stateHer face, a nod, clouds and a status line.
Meeting or Just meHow she's listening.

Three buttonsTranscript, Build prototype, Feedback.
Pause and EndTop right, through the whole session.
Part 06
Layouts I tried
Every layout I dropped was shaped around notes. The one that stuck put her answer in the middle.




Three versions



Landing page




Below the hero, a four-step walkthrough plays itself in a small window, with a pointer clicking through. Her face changes with each step, the same way it does in a session.
The three panels



After the call



The Library appears once you're signed in. Action items become a checklist, and every decision lands in one log.
Visual system
Aa
GabaritoThe interfaceAa
CaveatHer voiceAa
Space MonoSmall labelsWhat's next
No copy and paste. Claude Code pulls the latest plan, with the session's context attached.
Test the heads-up against recordings of meetings where I already know how things turned out.
Today she waits to be asked. The hard question is when interrupting is worth it.
She still catches who promised what. It needs a place on the new screen, for meetings.
Try it