Information, updates and resources live together.
Hands-on workshop Idea → live URL
Building a
web app using AI
We’re going to design, build, test and ship The Growing Club—together.
→ Use the arrow keys or the controls below
Develop the leader.
Programme information, learning and useful resources—in one place.
Open the club ↗judgment + AI speed
00 The destination
By the end, this will be real.
A useful home for the club—with a public welcome and shared information for its community.
This is not a talk about prompting.
It’s a build session. The room makes the product decisions. AI helps us move at the speed of the conversation.A public visitor understands what the club is.
A member can use it comfortably on a phone.
01 Requirements
Start with the problem,
not the prompt.
Three decisions we own
CEOs, mentors and organisers who return to use it—not just visit once.
Programme details, sessions, updates, learning and resources.
We decide what anyone can see and what stays within the group.
Definition of done · v0
The page must…
- ✓ Give the club a clear public introduction
- ✓ Make key information easy to find and update
- ✓ Organise resources around how members work
- ✓ Separate public and club information where needed
- ✓ Work on mobile, keyboard and screen reader
Our first question What should a member come back to this website to do every week?
Help us define a v1 information-sharing hub for a CEO mentoring club. Ask one question at a time.
Human: purpose + choices
02 Design · UI + UX
Make the experience visible
before we code it.
Good design gets someone from “what’s happening?” to the right information without making them think about the interface.
Two sides · one simple experience
- 01Welcome“What is this club?”
- 02Return“What’s new or next?”
- 03Find“Where is that resource?”
- 04Share“How do I add information?”
Claude Design explores visual directions and interaction ideas.
We choose what stays useful on the fifth visit—not just impressive on the first.
03 Build
Build in small,
visible loops.
Give AI the goal, the repo and the constraints. Then review real changes in a real browser.
- <main class="club-hub">
- <h1>What’s happening</h1>
- <section>Next club session
- and latest updates</section>
- <a href="/resources">Resources</a>
- </main>
in the club. Open resources ↗
The loop
- 1
Give contextGoal, design, repo, constraints
- 2
Build one sliceSee something useful quickly
- 3
Review the diffUnderstand what changed
- 4
Open the browserReact, adjust, repeat
CodexWorks across the repo, implements and verifies
Claude CodePairs on implementation, reasoning and debugging
04 Testing
AI can write it.
We still prove it.
We test the promise, the experience and the code—including the paths we did not expect.
Live test plan
5 checks05 Deploy
A web app isn’t finished
on localhost.
We turn the version on our laptop into a secure, shareable experience on the public web.
Release gate
- 1 Keep secrets out of the code
- 2 Build a preview before production
- 3 Check the live page on phone + laptop
- 4 Know how to roll back
AI prepares. The platform releases. We approve.
06 How we’ll work
One room. One build.
Every decision visible.
-
01
?
Frame
Say what success means
-
02
✦
Sketch
Compare real directions
-
03
</>
Build
Review each useful slice
-
04
✓
Prove
Try hard to break it
-
05
↗
Ship
Share the real URL
You bring
Context + taste Purpose, audience, judgment, final calls.AI brings
Speed + range Questions, options, code, checks, iteration.Together we make
Something useful Not “AI-generated.” Deliberately built.Ready when you are
Let’s build
The Growing Club.
The first line of code can wait.
The first good question can’t.
What should a member come back to this website to do every week?