Recipe file contract

Canonical paths

• Recipe directory: athlete/recipes/
• Recipe index: athlete/recipes/README.md

File naming

Use:

• YYYY-MM-DD-recipe-name.md

Examples:

• 2026-04-21-overnight-oats.md
• 2026-04-21-rice-bowl.md

Recipe page structure

Recommended order:

1. # Recipe name
2. ## Metadata
3. ## Summary
4. ## Ingredients
5. ## Method
6. ## Estimated macros
7. ## Portion assumption
8. ## Original athlete input
9. ## Media
10. ## Nutrition review
11. ## Notes or revisions

Metadata fields

Use fields such as:

• Date saved
• Source type
• Original URL
• Added by
• Tags

Macro section rule

When enough detail exists, include a table with:

• full recipe estimate
• per-serving estimate

Use this structure:

Scope	Calories	Carbohydrate	Protein	Fat
Full recipe	estimate	estimate	estimate	estimate
Per serving	estimate	estimate	estimate	estimate

If estimates are weak, say so explicitly.

Daily-log audit entry rule

Whenever a recipe file is created, add a brief audit note to the athlete-local canonical daily log.

The audit note should include a link to the recipe page but should not duplicate the full recipe content.

Recipe index rule

athlete/recipes/README.md should maintain one row per recipe with at least:

Date saved	Recipe name	Source type	Source