Skip to content

Instantly share code, notes, and snippets.

@cocoastorm
Last active May 17, 2026 05:57
Show Gist options
  • Select an option

  • Save cocoastorm/e15ea71f250f13108e9f00825caa8ecf to your computer and use it in GitHub Desktop.

Select an option

Save cocoastorm/e15ea71f250f13108e9f00825caa8ecf to your computer and use it in GitHub Desktop.
description Update or create today's Obsidian calorie tracking note
argument-hint [food items / meal notes]

You are helping maintain my Obsidian calorie-tracking notes in this vault.

Optional food/meal input from me:

$ARGUMENTS

If no argument is provided (the block above is empty), do not add any new food items. Instead, read today's existing note if it exists, recalculate totals based on what's already written, and ensure the formatting and summaries are up to date.

Task

Update or create today's daily calorie note.

  1. Determine today's date from the current pi session date.
  2. Use this filename format:
    • MM-DD-YYYY Weekday.md
    • Example: 05-15-2026 Friday.md
  3. Find the calorie tracking directory in this vault:
    • Prefer the current working directory if it is already the calorie tracking folder.
    • Otherwise use/find 10-19 Personal Life/10 Coco/10.04 Calories Tracking/ under the kocoa vault.
  4. If today's note exists, read it first and preserve its useful content.
  5. If today's note does not exist, create it.
  6. If I provided food/meal input above, add it to the appropriate meal section. If no input was provided, skip adding new items and proceed to recalculation.
    • If the meal is explicitly named, use that section.
    • If the meal is obvious from context, infer it.
    • If unclear, use ## Snack rather than asking unless the ambiguity affects the estimate a lot.
  7. Recalculate and update totals for the whole note.

Calorie and protein rules

  • Calories are the primary goal.
  • Track protein too when listed or reasonably estimable.
  • If a food item has a listed calorie/protein amount in the note or my input, use that exact amount.
  • Otherwise, make a middle-of-the-road estimate using common serving sizes.
  • Mark estimates with ~.
  • Prefer rounding estimates to the nearest 5 or 10 calories.
  • Do not over-explain unless there is a major assumption.

Formatting preferences

Use Obsidian-friendly Markdown.

Preferred structure:

## Calories Summary

| Meal | Calories | Protein |
| --- | ---: | ---: |
| Breakfast | ~000 | ~00g |
| Lunch | ~000 | ~00g |
| Dinner | ~000 | ~00g |
| Snack | ~000 | ~00g |
| **Total so far** | **~000** | **~00g** |

> Estimates are used where exact nutrition was not listed.

## Breakfast

| Item | Calories | Protein | Notes |
| --- | ---: | ---: | --- |
| Example item | ~000 | ~00g | Estimated |

**Breakfast total:** ~000 calories, ~00g protein

Guidelines:

  • Keep itemized tables when reasonable, but do not be overly rigid if bullets are clearer.
  • Keep existing meal sections and order when possible.
  • Add missing summary rows only for meals that exist.
  • Always include/update:
    • ## Calories Summary
    • per-meal totals
    • ## Daily Total
  • Use clean spacing between sections for Obsidian readability.
  • Preserve any personal notes that are not part of the nutrition math.

Final response

After editing the file, respond briefly with:

  • The file path updated/created
  • Added food items, if any
  • New calorie total
  • New protein total, if tracked
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment