Recipe capture

Handle durable recipe capture for Coach Luca.

Use this skill when an athlete explicitly wants to save a recipe for future use. The goal is to turn recipe links, text instructions, screenshots, and mixed recipe submissions into durable coaching assets inside the athlete workspace.

Workflow overview

1. Detect explicit recipe-save intent.
2. Classify the source as web link, text recipe, image recipe, or mixed input.
3. Ensure the canonical recipe storage paths exist.
4. Save one recipe Markdown file under athlete/recipes/.
5. Preserve the original source and any raw athlete text.
6. Save or reference any related media.
7. Add a brief daily-log audit entry with a link to the recipe file.
8. Update athlete/recipes/README.md.
9. Run the nutrition review immediately after recipe creation.

Read these references when needed

• Read references/workflow.md for the end-to-end recipe capture workflow and branch logic.
• Read references/file-contract.md for canonical paths, file naming, recipe page structure, and index rules.
• Read references/template.md for the standard recipe page template.

Core rules

• Trigger only on explicit recipe-save intent such as recipe, add recipe, save recipe, recipe for later, or log this recipe.
• Do not treat ordinary food photos, meal logs, or links as recipes unless recipe intent is clear.
• Preserve the original source URL, athlete text, and relevant media.
• Use one recipe file per saved recipe.
• Update the recipe index every time a recipe is created.
• Add a brief day-level audit entry to the canonical athlete daily log rather than copying the whole recipe there.
• Run the nutrition review immediately after recipe creation as part of the same workflow unless the run is explicitly test-only or operator-only.
• Write recipe nutrition reviews generically. Do not refer to the athlete by name inside the review body; use the athlete or other generic role-based phrasing instead.
• Do not rely on a separate review-status field or queue to track normal recipe completion.
• Use estimated macros only when there is enough detail to make a reasonable estimate.
• Clearly label full-recipe and per-serving macro values as estimated unless the source is reliable enough to support stronger confidence.
• When serving count is missing, make the best reasonable serving assumption and record that assumption explicitly.

Boundaries

This skill owns:

• recipe-intent detection
• canonical recipe file creation
• recipe index updates
• original-source preservation
• brief daily-log audit entry creation
• recipe index setup
• recipe media reference handling
• draft macro-estimate structure when enough input exists

This skill does not own:

• athlete-facing nutrition reply wording about the recipe
• detailed meal-plan synthesis beyond the capture record itself

This skill does coordinate the immediate nutrition review step as part of the same recipe-capture workflow.