Series: Weekend at Claude's — misadventures in building a production app with an AI anyone could mistake for the person who's going to make the whole thing happen
Here's the full prompt I gave Claude to kick off this feature:
Can you create a training, how to use webpage for the product? Also recommendations on how to add guided training in the mobile app. Lastly recommendations on a pre established private group 'my family' with some messages or events. This could be customized by the user. And a dummy public grocery group that they could see and later delete?
That's it. One paragraph, typed on my phone, no mockups, no wireframes, no specification document.
What came back — in a single session — was a fully designed training webpage, a 5-step in-app onboarding flow with complete React Native implementation specs, a My Family starter org with seeded content and rename behavior, four demo orgs (grocery, school, sports, church) with realistic post-by-post content for each, a Claude Code implementation prompt ready to hand off, a project knowledge document, and this blog post.
I reviewed it. I made two changes: rename should happen post-login, not during onboarding. And add a school, sports team, and church demo alongside the grocery one. One follow-up message.
That's the whole story of how this feature got designed.
Why this is possible
I want to be honest about what made that one-liner work. It wasn't magic. It was documentation.
Aphilaty has a set of project files that live alongside the code — CONTEXT.md, DECISIONS.md, HISTORY.md, TASKS.md, and the architecture doc. Every session, Claude reads them. Every decision we've made — the data model, the role hierarchy, what isSeedData means, why health list data is excluded from analytics pipelines, what the seed personas are named — all of it is written down.
So when I said "pre-established private group 'my family,'" Claude already knew the Firestore data model for orgs, that Krueger Grocery was our existing seed retailer persona, that isSeedData: true is a real flag with real pipeline implications, and that security rules changes need explicit approval before deploying.
The one-liner worked because months of prior thinking had been captured in writing. Claude didn't have to guess at the architecture. It could read it.
What the feature actually is
Since we're here: the first five minutes of Aphilaty now look like this.
You create an account. Before you've done anything, you belong to five groups.
My Family is a real org, owned by you, already containing a grocery list, a placeholder family dinner event, and a welcome message. It's not a tutorial — it's your group. You can rename it, invite people via join code, check off items, or delete the starter content and start fresh. It's yours.
The other four are read-only demos, clearly labeled, each showing a different kind of org that Aphilaty is built for:
Krueger Grocery — a retailer. BOGOF strawberries. A member discount on meat. A Saturday tasting event. This is what it looks like when your co-op or local store is on Aphilaty.
Whittier Elementary — a school. Mrs. Reale's supply list. Picture Day. A field trip permission reminder. This is what the school-to-parent channel looks like when it's not a Facebook group.
Westerville Rec Basketball — a sports team. Practice schedule. Game day. A snack duty sign-up with one slot already claimed. A carpool coordination message.
Grace Community Church — a faith community. Sunday service. A summer picnic volunteer list. The week's bulletin. A bookstore discount for members.
When you've seen enough, one tap removes any demo. It never comes back.
The five-step onboarding walkthrough runs in parallel: a 90-second guided tour of what orgs are, what you can share, and — the step we spent the most time on — why you're anonymous by default. Aphilaty's privacy model isn't a feature; it's the point. The onboarding is where we explain it plainly before someone has to find it in the FAQ.
The question that drove the design
There's one question I come back to for every product decision: what would make someone send this app to a friend in the first 24 hours?
Not after they've set up their family group perfectly. Not after they've figured out all the settings. But in the first hour, still in the new-app glow.
The answer has to be something they experienced, not something they read about. A snack duty list with a slot already claimed. A real grocery deal. A church bulletin. These are things millions of people try to coordinate every week across email threads and group chats and Facebook groups that are simultaneously too public and too chaotic.
We wanted you to see yourself in those orgs before you ever joined a real one.
The AI-assisted development loop in practice
This blog post is itself an example of the same thing. After the feature was designed, I asked Claude to draft the post with the theme of "how a one-liner produced all this with almost zero human effort aside from the ask and the review."
So here we are. One more follow-up. One more output.
The loop we've built is: I carry the product vision and make the calls. Claude carries the implementation detail and the documentation. Neither works as well without the other. The project files are the connective tissue — they're what let me stay in "what should we build" mode and stay out of "let me re-explain the architecture again" mode.
If you're building with Claude and you're not keeping a living context document, you're doing it the hard way. The one-liner only works when there's a year of thinking behind it, written down, ready to be read.
Aphilaty is a privacy-first community coordination app. aphilaty.com