I Built a System That Ends the Nightly Dinner Question
Four people, three sets of food rules, one iPad, and a free Google account. Here's what I built and the seven things I caught before handing it over.
By Darlene Killen, founder of The Visible Practitioner
A household I built for has four people and three sets of food rules that change depending on who’s home for dinner.
One adult can’t have dairy. The other won’t eat breakfast food at dinner.
The older teenager eats simple kosher style, but only on nights she’s home with the family. That’s once or twice a week in summer, five times during the school year.
The younger one eats anything.
Every night, somebody had to hold all of that in their head and come up with dinner.
They’ve got an iPad, an iPhone, and a Google account. No computer. Not technical.
So I built them a system that runs on exactly that.
If you've got a thing like this in your own life, that's what I do. You tell me what's eating your time, we build it together out of the tools you already have, and you never learn a new app. Details at the bottom.
The full walkthrough is in the setup guide I wrote for them, and I’m turning it into something anyone can use. More on that at the bottom.
What they already had
Nothing but a free Google account.
That was the whole constraint. No new subscriptions. No Zapier. No code. No app to learn.
What I built
Three pieces.
1. A Gem. A Gem is a saved assistant inside Gemini with a fixed set of instructions. Free on any Google account. You set it up once and it behaves the same way every time you open it.
All the intelligence lives in the instruction box. Nobody in the house has to remember a rule. The rules live in the tool.
2. A food list. I walked the kitchen and photographed everything, then cross-referenced it against a grocery receipt. That became one file, 161 items, with every dairy item flagged.
That file gets uploaded into the Gem as knowledge. Now the Gem knows what’s in the house.
3. A way to stay current. On grocery day they upload the receipt into the chat, and the Gem updates its picture of the kitchen. Before it commits to a meal, it asks if they still have the chicken.
What about food they eat during the week?
It doesn’t track that automatically, and I built it that way on purpose.
There’s no scanner, no app to open after dinner, no logging. Any system that needs someone to record every can of beans they open will be abandoned in a week.
So instead of tracking, it asks. Before the Gem commits to a meal, it checks: do you still have chicken? One question, answered in three seconds.
Then two things keep the picture close enough to true:
Grocery receipts get uploaded, so everything new is accounted for
The week always leads with whatever expires soonest, so perishables get used before they turn
It’s an approximation, not a live count. That’s the trade. A perfect inventory nobody maintains is worth less than a rough one that still works in six months.
That’s it. No spreadsheet to maintain. No live database. Nothing that breaks when I’m not there.
How it works now
They open the Gem and ask for the week. It gives back a pool of about five dinners plus grazing options, ordered so whatever expires soonest gets eaten first.
Not a schedule with assigned nights. A pool. They slot meals in as the week actually goes.
After a meal, the Gem asks whether that was a favorite or a skip. Over time it builds a yes list and a no list on its own.
The part that took the longest
I generated a full week of meals at real quality and read it the way they’d read it. Before handing anything over.
Seven things were wrong.
One. It said dairy on the side was fine for the kosher teenager on a meat night. It isn’t. Meat and dairy can’t be at the same sitting at all. No amount of testing catches that. You have to know the rule.
Two. The recipes had no measurements and no numbered steps. Fine if you cook by feel. Useless at 6pm when you’re fried.
Three. It invented food. Salsa and fries nobody owned.
Four. Some meals were technically compliant and genuinely inedible. Nobody was eating that.
Five. It assigned specific nights when they needed a pool.
Six. It ignored what expires first.
Seven. It mixed up whose rules were whose. It put the kosher rules on the adult who doesn’t keep kosher. She can eat meat and cheese together, she just can’t have dairy.
Five, six, and seven only showed up because I read a full week end to end. A quick spot check would’ve missed all three.
The audit is the product. The AI does the assembly. Somebody still has to know what wrong looks like.
What I tried first and threw out
Photo-based inventory that updates continuously. Too much recurring work for them.
Google Sheets with Apps Script automation. Too complex for an iPad-only, non-technical setup.
A live Google Drive connected database. One more thing that can break.
Every architecture I liked got cut for being fragile in someone else’s hands.
One unglamorous thing nobody tells you
The original build thread got so long that photo uploads stopped working. Screenshots failed too.
A fresh chat fixed it. That’s the kind of thing you only learn by doing this over and over.
Something you can try today
Pick the thing you re-decide every single day.
Open Gemini or Claude or ChatGPT and tell it, in plain words, what it needs to know to make that decision for you. Every rule, every exception, who it applies to and when.
Then ask it to do the thing.
Then read what it gives you like the person who has to live with it. That’s where you’ll find what’s wrong.
What annoys the shit out of you?
What’s the thing you’d love an AI tool to just handle?
Chances are we can figure it out together, without you learning a new app. You just talk to Claude or Gemini or ChatGPT, and the AI does the backend work.
Tell me what it is. I build these for people.