Build a simple food log app to track what a picky toddler eats with Claude Code

Posted

Oct 9, 2026 by Sergio Fajardo Jr (@sergiofajardojr)

·

Last checked

Oct 22, 2026

·

Method:

How we verify

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Outcome

Sergio Fajardo Jr's son is 2, a picky eater, and has been on the 1st percentile for weight since birth. Fajardo built a small web app with Claude Code so both parents can log every food they offer and how far their son gets with it: ignored, touched or ate. It takes four taps per food, and Fajardo says they can now see what's working.

AI tool

Claude Code

The source didn't share its exact prompt, so we wrote this from what it describes.

What the prompt labels mean

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Build a very simple app our family can use to log foods we offer our child and how they respond.

What I can give you (ask for whatever's missing):
- Who will use it and on what devices: [USERS AND DEVICES]
- What to record for each food (for example ignored, touched, ate): [OPTIONS]
- Where it should run or be hosted: [HOSTING]

This is admin help, not medical advice. Don't diagnose or suggest treatments. If anything I mention sounds urgent, tell me to contact a doctor or emergency services first.

Rules:
- Keep logging to a few taps per food, usable one-handed at the table.
- Show simple patterns over time, such as foods that moved from ignored to ate.
- Keep the data private to our family, with no public link and no third-party tracking.
- Explain how to run and update it in plain language.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A working app, how to open it on our phones, and how to back up the data.

You'll know it worked when: both of us log meals in seconds and can see which foods are working.

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Build a very simple app our family can use to log foods we offer our child and how they respond.

What I can give you (ask for whatever's missing):
- Who will use it and on what devices: [USERS AND DEVICES]
- What to record for each food (for example ignored, touched, ate): [OPTIONS]
- Where it should run or be hosted: [HOSTING]

This is admin help, not medical advice. Don't diagnose or suggest treatments. If anything I mention sounds urgent, tell me to contact a doctor or emergency services first.

Rules:
- Keep logging to a few taps per food, usable one-handed at the table.
- Show simple patterns over time, such as foods that moved from ignored to ate.
- Keep the data private to our family, with no public link and no third-party tracking.
- Explain how to run and update it in plain language.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.

Output: A working app, how to open it on our phones, and how to back up the data.

You'll know it worked when: both of us log meals in seconds and can see which foods are working.

Before you start, ask me 1–3 short questions about anything important that's missing below. Keep them quick. Then do the task, checking in with me at the key points.

Goal: Build a very simple app our family can use to log foods we offer our child and how they respond.

What I can give you (ask for whatever's missing):
- Who will use it and on what devices: [USERS AND DEVICES]
- What to record for each food (for example ignored, touched, ate): [OPTIONS]
- Where it should run or be hosted: [HOSTING]

This is admin help, not medical advice. Don't diagnose or suggest treatments. If anything I mention sounds urgent, tell me to contact a doctor or emergency services first.

Rules:
- Keep logging to a few taps per food, usable one-handed at the table.
- Show simple patterns over time, such as foods that moved from ignored to ate.
- Keep the data private to our family, with no public link and no third-party tracking.
- Explain how to run and update it in plain language.
- Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify.
- Add a simple export we could share with our pediatrician if they ask.

Output: A working app, how to open it on our phones, and how to back up the data.

You'll know it worked when: both of us log meals in seconds and can see which foods are working.

Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.

Source

https://x.com/sergiofajardojr/status/2108515126550974683