Format the provided recipe data as a markdown file and save it.
Input
The recipe data may arrive in any of these forms — handle all of them:
- Pasted raw text (e.g. copied from a website or book): parse it to extract the fields below.
- Structured data (JSON, YAML, or similar): read the fields directly.
- File path: read the file at that path first, then parse.
- Interactive / incomplete input: if critical fields are missing (title, ingredients, steps), ask the user to provide them before proceeding.
The recipe data is: $ARGUMENTS
Output format
Save the recipe as a markdown file. Use the recipe title with appropriate title casing as filename, e.g. Broccolini Soba Noodle Salad.md. Save it in the current working directory unless the user specifies otherwise.
The file must follow this exact structure:
---
tags:
- recipe
- <category tag(s), e.g. breakfast, salad, soup, stew, vegetable, chicken, meat, fish, pasta, dessert>
- <vegetarian if vegetarian>
- new
serves: <number>
preptime: <number of minutes>
cooktime: <number of minutes>
source: <book or website name>
---
## Ingredients
- [ ] <ingredient 1>
- [ ] <ingredient 2>
…
## Comments
<Any notes, tips, or description about the dish. If none provided, omit this section entirely.>
## Steps
1. <Step 1>
2. <Step 2>
## Per Serving
* <number> kcal
* <number>g protein
* <number>g fat
* <number>g carbohydrates
…
Rules
- ALWAYS stay true to the original data, nevert change the text, never make things up.
- Tags: always include
recipe. Always include new. Include vegetarian if the dish is vegetarian. Infer category tags from the ingredients and dish type. Choose from: breakfast, salad, soup, stew, vegetable, chicken, meat, fish, pasta, dessert, dressing. Add dish tags like high-protein, meal-prep where appropriate. Only add tags that are clearly justified.
serves, preptime, cooktime: use integers.preptime is active preparation, cooktime is additional time cooking. If only one is provided, list it as preptime. If preptime/cooktime are not provided, omit the fields.source: use the book title, website name, or "Unknown" if not provided.- Ingredients: use
- [ ] checkboxes. Include quantities and units.
- Steps: use a numbered list. Be clear and concise.
- Per Serving: Include kcal, protein and fat if present. If data is not present, omit this section.
- After saving the file, confirm the filename and path to the user.
1---2name: recipe3description: Format recipe data into a structured markdown file with YAML frontmatter, ingredients checklist, comments, and steps sections.4---56Format the provided recipe data as a markdown file and save it.78## Input910The recipe data may arrive in any of these forms — handle all of them:1112- **Pasted raw text** (e.g. copied from a website or book): parse it to extract the fields below.13- **Structured data** (JSON, YAML, or similar): read the fields directly.14- **File path**: read the file at that path first, then parse.15- **Interactive / incomplete input**: if critical fields are missing (title, ingredients, steps), ask the user to provide them before proceeding.1617The recipe data is: $ARGUMENTS1819## Output format2021Save the recipe as a markdown file. Use the recipe title with appropriate title casing as filename, e.g. `Broccolini Soba Noodle Salad.md`. Save it in the current working directory unless the user specifies otherwise.2223The file must follow this exact structure:2425```26---27tags:28- recipe29- <category tag(s), e.g. breakfast, salad, soup, stew, vegetable, chicken, meat, fish, pasta, dessert>30- <vegetarian if vegetarian>31- new32serves: <number>33preptime: <number of minutes>34cooktime: <number of minutes>35source: <book or website name>36---3738## Ingredients3940- [ ] <ingredient 1>41- [ ] <ingredient 2>42…4344## Comments4546<Any notes, tips, or description about the dish. If none provided, omit this section entirely.>4748## Steps49501. <Step 1>512. <Step 2>5253## Per Serving5455* <number> kcal56* <number>g protein57* <number>g fat58* <number>g carbohydrates59…60```6162## Rules6364- ALWAYS stay true to the original data, nevert change the text, never make things up.65- Tags: always include `recipe`. Always include `new`. Include `vegetarian` if the dish is vegetarian. Infer category tags from the ingredients and dish type. Choose from: breakfast, salad, soup, stew, vegetable, chicken, meat, fish, pasta, dessert, dressing. Add dish tags like `high-protein`, `meal-prep` where appropriate. Only add tags that are clearly justified. 66- `serves`, `preptime`, `cooktime`: use integers.67- `preptime` is active preparation, cooktime is additional time cooking. If only one is provided, list it as `preptime`. If `preptime`/`cooktime` are not provided, omit the fields.68- `source`: use the book title, website name, or "Unknown" if not provided.69- Ingredients: use `- [ ]` checkboxes. Include quantities and units. 70- Steps: use a numbered list. Be clear and concise.71- Per Serving: Include kcal, protein and fat if present. If data is not present, omit this section.72- After saving the file, confirm the filename and path to the user.
walkenho