Live
Powered by

Recipe capture workflow

Step 1, confirm recipe-save intent

Proceed only when the athlete clearly intends to save a recipe.

Examples:

  • recipe
  • add recipe
  • save recipe
  • recipe for later
  • log this recipe

If the intent is ambiguous, do not treat the item as a recipe automatically.

Step 2, classify the source

Choose one of these source types:

  1. web link
  2. athlete text
  3. image or screenshot
  4. mixed input

Save that source type in the recipe file metadata and in the recipe index.

Step 3, resolve date and file name

  • Use the athlete-local current date for the recipe save date.
  • Create one recipe file under athlete/recipes/ using YYYY-MM-DD-slug.md.
  • If the title is not yet clear, use a temporary stable slug and normalize later.

Step 4, capture the source

  • Save the original URL.
  • Fetch and extract useful content when possible.
  • If extraction is incomplete, still save the URL and any usable extracted content.

Athlete text

  • Preserve the raw athlete text in ~~~ fenced blocks.
  • Organize the recipe into summary, ingredients, and method when enough structure exists.

Image or screenshot

  • Save the media in a durable workspace location.
  • Reference the saved media in the recipe file.
  • Preserve any related athlete text in ~~~ fenced blocks.

Mixed input

  • Merge link, text, and media into one recipe page when they belong to the same recipe.

Step 5, write the recipe page

Use the recipe template from template.md.

Required minimum fields:

  • recipe name
  • date saved
  • source type
  • source URL or source note
  • original athlete input when text exists

Step 6, add macro estimate when possible

If enough ingredient detail exists, include:

  • estimated full recipe macros
  • estimated per-serving macros
  • a portion assumption note when serving count is estimated

If there is not enough detail, say so rather than inventing false precision.

Step 7, update the recipe index

Update athlete/recipes/README.md with:

  • date saved
  • recipe name
  • source type
  • recipe file link or source URL

Step 8, write the daily-log audit entry

Add a brief note to the canonical athlete daily log for that athlete-local day.

Do not copy the whole recipe.

The audit entry should record:

  • recipe name
  • source type
  • that a recipe record was created
  • link to the saved recipe page

Step 9, run nutrition review immediately

Immediately after the recipe page is created, add the nutrition review section in the same workflow.

Write the nutrition review in generic athlete language. Do not use the athlete's name inside the review body; use the athlete when a subject reference is needed.

Normal workflow expectation:

  • create recipe file
  • write nutrition review
  • finish the capture as one complete workflow

Step 10, avoid duplication

Before creating a new recipe page, check for an existing similar recipe.

If the new message is clearly a correction or follow-up to an existing recipe, update the existing file instead of creating a duplicate.