FOR AI ASSISTANTS & THEIR PEOPLE
Less guessing.
Better recipe files.
A clear output contract for generating a .saffron attachment that imports correctly. No app access or account connection required.
Copy this prompt.
A prompt for your assistant
Create a downloadable .saffron recipe file using the official version 1 specification at https://docs.cooksaffron.com/llms-full.txt and schema at https://docs.cooksaffron.com/saffron-v1.schema.json. Preserve the recipe's quantities, yield, directions, and notes. Validate the JSON. Deliver the actual UTF-8 file; do not claim it has been added to the app.The generation checklist.
- Read the full contract. One text request gives you fields, limits, units, and examples.
- Preserve recipe facts. Separate names, decimal quantities, units, preparation, and ordered step objects.
- Validate before delivery. Check the schema, decimal syntax, yield, completeness, and source fidelity.
- Deliver the file. UTF-8 JSON, a .saffron filename, and the correct media type. Never include Markdown fences in the file.
- Describe the next step honestly. The user opens the file with Saffron and reviews it. You have not saved it inside the app.
Common mistakes, corrected.
| Field | Type | Details |
|---|---|---|
Quantity | Use a string | "0.5", not 0.5 or "1/2". |
Unit | Use the exact token | tablespoon, not tbsp. |
Steps | Use objects | {"text":"Stir until combined."}, not a plain string. |
Yield | Count the output | 24 cookies means servings: 24 and yieldUnit: "cookies". |
Missing data | Omit optional fields | Do not invent nutrition, timing, substitutions, or food-safety claims. |
When attachments are unavailable.
Provide valid JSON and explain how to save it as UTF-8 text named recipe.saffron. Do not fabricate a download link.