lextoumbourou/lex-skills/food-log

Food Log

When the user reports something they ate (text description, food photo, or nutrition-label photo), resolve its macros and log it to today's daily note. Never skip the lookup order.

Configuration

Adapt these to the vault (defaults shown):

• Common foods note: health/common-foods.md — foods the user eats regularly, per-serving macros in category tables
• Recipes folder: recipes/
• Daily notes: daily/YYYY-MM-DD.md with a ## Macros section and calories_consumed frontmatter field
• Daily targets: ask the user for their calorie and protein targets on first use and record them here

Resolving macros (in this order)

1. The common-foods note — ALWAYS check first. Match loosely ("quest bar", "the choc protein shake") and scale by the serving reported. If it's there, use those numbers — don't re-estimate.
2. Nutrition-label photo: read the panel directly; scale to the amount eaten. (Per-100g vs per-serving matters — check which column you're reading.)
3. Home-cooked meal by name (e.g. "bolognese"): check the recipes folder for the recipe; estimate per-serve macros from its ingredients. If the user will eat it again, add the per-serve result to common-foods.
4. Food photo: identify what's in it. If you can tell it's an exact known item (branded product, or something already in common-foods), use the common-foods entry — the photo then only confirms portion size. Otherwise estimate each component's portion from the photo and state your assumptions ("assuming ~150g rice").
5. Neither: estimate from knowledge, say you estimated, and give the assumption that most affects the number.

Logging

1. Add a row to today's ## Macros table: | Item | Cal | Protein | Carbs | Fat |. Update the Total row.
2. Update calories_consumed in today's frontmatter to the new total (and modified, if the vault tracks it).
3. Reply with the item's cal + protein and the running day total vs the user's targets. Flag if a typical dinner would blow the budget.

Maintaining the common-foods note

• New packaged/branded item or anything the user is likely to eat again → append it to the right category table (same columns; note flavour/variant). Tell the user you added it.
• Don't add one-off restaurant meals or wild estimates — only entries with numbers worth reusing.
• Respect inline notes in the file (e.g. a default variant for a regular order).

Notes

• Food/label photos do NOT get embedded in the daily note — just log the macros.
• If an end-of-day rollover to a calorie log exists (see a morning-routine skill), that owns the rollover — this skill only logs items.