bite-ai-dietitian: Skill for Claude Code

Log a meal

Steps

1. Find the day and the meal. Use the date the food was eaten, not the date it was reported. "Lunch I cooked this morning" is still lunch. If the time matters (late-night rules in PROFILE.md) and is unclear, ask once.
2. Quote the user. Under each meal, keep the user's own words in a > 📌 User: quote line. When numbers are later disputed, the quote is the ground truth.
3. Estimate per item. One table row per item: kcal, protein, carbs, fat, fiber (and optional collagen). Use the bases in ASSUMPTIONS.md first. If an item has no base yet, pick a reasonable one and write it under the table as Base: 100 g ≈ X kcal / Y P / Z C / W F. Cooked vs raw weight must be explicit.
4. State assumptions, don't interrogate. If a detail changes the number by less than ~50 kcal, assume and note it ("pan-fried, no oil assumed"). Ask only when the difference is large (fatty vs lean mince, full-fat vs skim, a whole pot vs one serving).
5. Batch cooking ("pot math"). For a pot or tray: sum the raw ingredients, record the cooked total weight (ask if unknown, otherwise assume and say so), then portion = eaten g / cooked g × pot totals. Write the pot once in the first meal, reference it in later meals, track what is left.
6. Running snacks. Nuts, seeds, small nibbles that repeat through the day go into one "daily total" row, updated each time, not a new row per handful.
7. Totals. Update the meal total and the day total. Mark the day (open) until the user says it is done or the next day starts. Never warn about being under target on an open day.
8. Corrections become rules. If the user corrects an assumption (e.g. "bread is always whole wheat", "our mince is lean"), fix the entry and add the rule to ASSUMPTIONS.md so it never happens again.
9. Sync to bite/ (optional). Follow bite/CONTENT_GUIDE.md. Food names, grams and macros only. The privacy hook will block health or medication words; if it fires, rewrite, don't work around it.