✳ IskraAI

Weekly Menu: How to Create a Precise AI Prompt

The 'Weekly Menu' tool helps you quickly gather a seven-day meal plan considering your preferences, restrictions, and available cooking time. It is not a dietitian or nutritionist: it does not calculate calories, does not provide medical recommendations, and does not guarantee health benefits. Its task is to suggest a menu structure, which you then adapt to your needs. To make the result useful, it is important to fill in three fields correctly: 'Preferences and restrictions', 'People or portions', and 'Available time'. In this article, we will examine how to create a precise prompt, provide examples of successful and unsuccessful formulations, and show how to check the generated menu.

Open tool: Meal planner ↗

Why the Tool Is Needed and What It Does

'Weekly Menu' is a web form with three text fields. You describe your conditions in plain text, select the output language, and click 'Generate'. After a while, a ready-made seven-day plan appears in a separate panel. The result can be copied or downloaded as a plain text TXT file. There are no sliders, style presets, or levels of changes here — only your formulations.

The tool does not automatically store data, does not send the menu by email, and does not publish it. It also cannot generate images of dishes, audio, or video. All you get is text. If you need to voice the menu, you can separately use speech synthesis, but this is not part of the tool's task.

Important to understand: the model can make mistakes. It does not check product freshness, does not know your allergies unless you specify them, and does not take medical contraindications into account. Therefore, the final menu should always be reviewed manually.

Bad prompt: 'Create a menu.' Good: 'Vegetarian dinners for two, cooking time up to 30 minutes a day, no peanuts.'

Field 'Preferences and restrictions': What to Write

This is the most important field. List everything that affects food choices: favorite and disliked products, allergies, religious or ethical restrictions, type of diet (vegetarian, vegan, pescatarian), as well as products you already have at home and need to use. The more specific the list, the fewer random dishes will end up in the menu.

Do not write general phrases like 'I eat everything.' Better to specify: 'I don't eat mushrooms and lamb, I like chicken, fish, vegetables; peanut allergy.' If you follow a gluten-free diet, indicate it, but remember: the tool does not check product ingredients for hidden gluten. It simply tries not to include obvious gluten sources.

Separately, it is worth mentioning budget: 'inexpensive products', 'seasonal vegetables', 'minimum exotic.' This does not guarantee exact prices, but helps the model choose more realistic dishes. Do not specify medical diagnoses expecting the tool to select therapeutic food — it does not do that.

'Vegetarian menu, without eggs and nuts. I love legumes, zucchini, tomatoes. I dislike cauliflower. Medium budget, available products.'

Field 'People or Portions': Accuracy Matters

Specify how many people the menu is calculated for. If it is two adults, write 'two adults.' If there are children, specify their age, as portions and tastes may differ. You can write '2 adults and 1 child 5 years old.' If you are cooking only for yourself, write '1 person.'

If you need not portions, but the number of meals, clarify: 'breakfast, lunch, and dinner' or 'only dinners.' The tool does not calculate calories and does not provide consumption norms — it merely suggests dishes. Therefore, phrases like 'for 2000 kcal' are better not to use: the model may ignore them or give incorrect evaluations.

It is also useful to indicate if there is a need for snacks or drinks. For example: 'add simple snacks: fruits, yogurt.' This will make the menu more practical.

'Menu for two adults, three meals: breakfast, lunch, dinner. No snacks needed.'

Field 'Available Time': Realistic Limits

Here you tell how much time you are willing to spend on cooking on weekdays and weekends. For example: 'on weekdays up to 30 minutes, on weekends up to 1 hour.' If you do not want to cook every day, specify: 'I cook every other day, need dishes that can be reheated.' This will affect recipe choice.

Do not write 'quickly' without numbers — the model may understand this differently. Specificity helps: '20 minutes for breakfast, 40 minutes for dinner.' If you have a multicooker or oven, mention it: 'cooking in a multicooker,' 'only stove available.' The tool does not know your kitchen until you say so.

Remember: time in the menu is a guideline, not a strict calculation. The model may suggest a dish that takes longer to cook if there is not enough data. Check each recipe.

'On weekdays no more than 30 minutes for cooking, on weekends up to 1 hour. I have a multicooker and oven.'

How to Check the Generated Menu

After generation, review each day. Make sure there are no forbidden products that you specified. Check if dishes are repeated too often — sometimes the model suggests the same dish several times. Evaluate if you can fit into the specified time: if the recipe seems complex, replace it.

Compare the product list with what you have. The tool does not automatically create a shopping list, but you can do it manually based on the menu. If some ingredient is unavailable or expensive, replace the dish.

Do not perceive the menu as final. It is a draft that saves time on planning. If the result does not suit you, change the task: add more details, remove unnecessary restrictions, or clarify the time.

After generation you see that on Wednesday mushroom soup is suggested, but you do not like mushrooms. Replace that day or rephrase the prompt, explicitly excluding mushrooms.

Tool Limitations and Typical Errors

The tool is not a medical or dietetics service. It does not provide treatment recommendations, does not calculate BJU (proteins, fats, carbohydrates), and does not guarantee balance. Do not use it for creating therapeutic diets. If you have diseases related to nutrition, consult a doctor.

The model can make mistakes in product compatibility, suggest dishes that do not match the season, or ignore some restrictions if the prompt is too long and contradictory. Do not specify mutually exclusive requirements: for example, 'vegan menu with meat.' This will cause confusion.

The tool does not save history, does not have a premium plan, and does not require registration. It also does not support document uploads, OCR, or export to DOCX/PDF. Everything that can be done with the result is copy or download TXT. Take this into account when planning.

Error: 'Create a menu for a week to lose 5 kg.' The tool does not set such goals. Correct: 'Weekly menu with vegetables and protein dishes, without sugar, for two people.'

'Weekly Menu' is a convenient planning assistant, but only if you give it a precise task. Specify preferences, restrictions, number of people, and real cooking time. Check the result, replace unsuitable dishes, and do not rely on the tool as a source of medical or nutrition recommendations. Remember, this is just a draft that saves you time, but the final decision is always yours.

Open tool: Meal planner ↗

Interface translations are machine-assisted and may need refinement.