log-food

name	log-food
description	Log what was eaten today. Use when the user says "we had X for dinner", "ate X", "log food", or mentions what they ate.
user-invocable	true
argument-hint	[what was eaten, e.g. 'salmon teriyaki with rice and broccoli']
allowed-tools	Read, Write, Edit, Glob

Log food following docs/food-tracking-process.md.

What was eaten: $ARGUMENTS

Process

1. Check if data/food/YYYY-MM-DD.md (today's date) already exists
2. If it exists, read it and append the new entry under the appropriate meal section
3. If it doesn't exist, create it

File format

# Food — YYYY-MM-DD

## Dinner
- <what was eaten>

## Lunch
- <if mentioned>

## Snacks
- <if mentioned>

Estimated macros

Only add this section when the user explicitly asks for macro estimates or a calorie breakdown. This section is parsed by the dashboard to render inline charts.

Required format (the dashboard parses these exact patterns):

## Geschatte macro's

~<total> kcal totaal
- Eiwit: <g>g (<pct>%)
- Koolhydraten: <g>g (<pct>%)
- Vet: <g>g (<pct>%)

<Meal1>: <kcal> kcal | <Meal2>: <kcal> kcal | <Meal3>: <kcal> kcal

• Estimate per ingredient, then sum per meal
• Use kcal conversion: protein 4 kcal/g, carbs 4 kcal/g, fat 9 kcal/g
• The per-meal kcal line enables a stacked bar chart in the dashboard
• Don't obsess over precision — reasonable estimates are fine
• If only a single meal is logged and the day isn't complete, skip the macro section

Guidelines

• Keep entries concise but specific enough to be useful later ("salmon teriyaki with rice and steamed broccoli" not just "fish")
• If the user doesn't specify the meal type, assume dinner (most common)
• Don't ask for calorie counts — keep it lightweight
• If something sounds particularly quick or easy, note it (useful for future suggestions)
• If it's a new recipe they haven't had before, note that too