When should you use it?
- You cook from a set of favorite recipes
- You want nutrient totals without an app
- You are tracking symptoms with food
Not for: Diagnosing allergies or intolerances; Restrictive diets without medical advice
What do you need, and what do you get?
You need
- Recipe files or photos
- Nutrition database access
- Symptom log
You get
- Recipe library with nutrition
- Weekly plan and shopping list
- Nutrient report
- Pattern notes for your doctor
How does it work, step by step?
- Add recipesDrop photos, PDFs or links into a meals folder and let the agent transcribe them.
- Fetch nutritionLook up each ingredient in a public nutrition database and store totals.
- Plan the weekPick meals or let the agent combine them, then generate a list by category.
- Check nutrientsReview daily protein and vitamins and small tweaks to fill gaps.
- Log symptomsRecord symptoms daily; review patterns with a clinician before any elimination diet.
The prompt
Our own prompt, inspired by u/blythmar on r/ClaudeAI and written to work in Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Recipe files are in {meals_folder}. For each new recipe, extract ingredients and quantities, look up nutrition in {nutrition_source}, and save per-serving totals. Plan {days} days using {preferences}. Return a shopping list by category and a daily nutrient table. From {symptom_log}, list possible food patterns as questions for my doctor, with the dates behind each.
Inspired by u/blythmar on r/ClaudeAI: How I'm using Claude Code for Meal Planning and Symptom Tracking. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Two weeks of data is too little to be sure; the poster calls it a first hypothesis.
- Nutrition lookups can match the wrong food; spot-check entries.
Our take
Keeping recipes as files the agent can read is a quietly powerful choice. Planning, nutrition and shopping all come from one source you control. The symptom log is the most sensitive part; treat what it finds as a question to raise with a professional, which is how the poster frames it too. Keep recipe files in plain text so they stay readable outside any one tool, and date each symptom entry. Share medical concerns with a clinician, not only the model. Exclude known allergens explicitly in the plan prompt every week. Nutrition lookups can match the wrong food, so spot-check a few entries in each recipe. Two weeks of data is too little to be sure of anything; the poster treated tomatoes as a first hypothesis, not a finding. Review patterns with a clinician before starting any elimination diet. Keeping recipes as plain files also means you can switch tools later without losing your library or your notes.
Where the time goes back: Planning, shopping lists and nutrient math run from your own recipes instead of a separate app.
FAQ
Do I need to code?
Should I stop eating a food based on this?
Source and credit
Inspired by u/blythmar on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How I'm using Claude Code for Meal Planning and Symptom Tracking
- Creator
- u/blythmar on r/ClaudeAI
- Published on
- Original date
- Jan 5, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.