What to cook: how to get a practical recipe from available products
The "What to cook" tool helps turn a list of available products into specific culinary ideas. Unlike ordinary recipe search, here you yourself set the ingredients, their quantity, dietary preferences, number of portions and available time. Based on this data, the tool offers a text recipe. In this article we will tell you how to correctly fill in the fields, how to formulate requests to get realistic suggestions, and what to pay attention to when checking the result. The material is oriented to practice: you will learn not just to copy the answer, but to consciously work with the tool and evaluate its suggestions.
Open tool: Recipe generator ↗How the tool works and what it takes as input
"What to cook" is a web form with text fields. You enter ingredients and their quantities, preferences and restrictions (for example, vegetarianism or gluten-free), number of portions or people, and also available time for cooking. After pressing the "Generate" button, a single text result appears in a separate panel. It can be copied or downloaded in TXT format. The tool does not save query history, does not perform batch processing and does not have integrations with other services. This means that each request must be entered anew, and the result must be saved independently if you need it.
Input fields have restrictions: the first field - up to 8000 characters, details field - up to 1000 characters. This is enough to list products, their quantity and special wishes. For example: "potatoes - 4 pcs., carrot - 2 pcs., onion - 1 pc., lentils - 200 g, tomatoes - 3 pcs.". The more precisely you describe ingredients and their volume, the more relevant the suggestion. If you indicate only names without quantities, the tool may suggest a dish for which you do not have enough products.
The tool does not generate images or audio. Vector images (SVG, PNG) and speech via eSpeak (WAV) are not related to the task of selecting recipes. Focus on textual description: it is this that contains practical value.
Input example: ingredients: potatoes 4 pcs., carrot 2 pcs., onion 1 pc., lentils 200 g, tomatoes 3 pcs.; restrictions: vegetarianism; portions: 2; time: 30 minutes.
Practical example: from request to result
Let's consider a scenario. You have potatoes, carrots, onion, lentils and tomatoes. You want to cook dinner for two in 30 minutes and follow vegetarianism. You enter these data into the form. The tool may suggest, for example, lentil stew with vegetables or soup with lentils and tomatoes. It is important that the suggestion takes into account the time: 30 minutes is a limitation, so the recipe should be quick. If the tool suggests a dish requiring long simmering, this is a mismatch. You can clarify the request, adding "quick" or "without oven".
After receiving the result, check it for realism. Is there enough of the specified quantities? For example, if a recipe requires 500 g of lentils, and you only have 200 g, the suggestion is not feasible. Also make sure all ingredients are available and do not contradict restrictions. If you are a vegetarian, the recipe should not contain meat or fish. The tool may make mistakes, so always analyze the text.
Another aspect - the sequence of actions. A good recipe contains clear steps: chopping, frying, boiling. If steps are skipped or illogical, the result requires editing. You can re-formulate the request, adding "step-by-step recipe" or "detailed instructions". This will help get a more structured answer.
Possible answer: "Lentil stew with vegetables. Fry onion and carrot, add potato and tomatoes, simmer 15 minutes. Add lentils and simmer another 5 minutes. Season to taste."
How to formulate requests for precise results
To get a useful recipe, clearly specify all parameters. Start with listing ingredients and their quantities. Use understandable units of measurement: grams, pieces, milliliters. If there are products that need to be used first, indicate this. For example: "need to use lentils and tomatoes". This will help the tool focus on them.
Specify restrictions explicitly. If you have a gluten allergy, write "gluten-free". If you do not eat meat, specify "vegetarianism". You can add "lactose-free" or "nut-free". The more restrictions, the narrower the choice, but the result will be safer. Do not forget about the number of portions: "for 2 people" or "2 portions". This affects proportions.
Time is a critical parameter. If you only have 20 minutes, write "20 minutes". The tool should suggest a dish that can be cooked in this time. If it suggests something longer, clarify the request: "only quick recipes". You can also specify cuisine preferences: "Italian", "Asian" - but this is not mandatory.
Clarified request: "Ingredients: potatoes 4 pcs., carrots 2 pcs., onion 1 pc., lentils 200 g, tomatoes 3 pcs. Restrictions: vegetarianism, gluten-free. Portions: 2. Time: 30 minutes. Preferably quick stew."
Checking the result: criteria and typical errors
After generating the recipe, check it by several criteria. First, compliance with ingredients: were all products from the list used? If there is an ingredient in the recipe that you do not have, this is an error. Second, compliance with restrictions: are there any forbidden products? Third, realism of time: does the cooking fit into the specified time? Fourth, logic of steps: is it clear what to do?
Typical tool errors: suggesting a dish requiring more time than indicated; using ingredients not in the list; ignoring restrictions (for example, adding meat when vegetarianism). There may also be inaccuracies in proportions: for example, too much salt or spices. Sometimes steps may be incomplete. In such cases you can adjust the request and generate again.
If the result is unsatisfactory, try changing the formulation. For example, instead of "quick" write "in 30 minutes". Instead of "vegetarian" - "without meat and fish". You can add "simple recipe" or "minimum ingredients". Experiment with formulations to understand how the tool responds to different input data.
Check: the recipe says "simmer 40 minutes", but you only have 30. This is a mismatch. You need to clarify the request: "strict cooking time up to 30 minutes."
Tool limitations and how to take them into account
"What to cook" is not a professional culinary advisor. It generates text based on entered data, but may contain errors. It does not take into account seasonality, product availability in stores, your culinary skills or equipment. For example, it may suggest a dish requiring a blender, which you do not have. Therefore always assess realism.
The tool does not save your queries and does not have history. If you want to return to the recipe, copy it or download in TXT. There is no batch processing, so each request is processed separately. There are no integrations with other services, so you cannot send the recipe by email or publish it directly. All this limits automation, but allows you to focus on manual verification.
The tool also does not generate images or video. Vector images (SVG, PNG) may be available, but they are not photorealistic. eSpeak (WAV) speech and SRT subtitles are not related to recipes. Do not expect the tool to offer a photo of the dish. This is a text utility.
Limitation: the tool does not know that you do not have an oven. If a recipe requires baking, you need to adapt it or choose another one.
Teaching strategies with the tool
Use the tool to practice menu planning skills. Start with a simple request, then complicate: add restrictions, reduce time, increase number of portions. Compare results. This will help you learn to formulate clear instructions and evaluate culinary ideas. You can also practice adapting recipes: if the suggestion is not ideal, try to change it yourself.
Keep a journal of requests and results. Record which formulations gave the best result. For example, "specifying exact time helped get a quick recipe". This will develop your intuition. It is also useful to analyze errors: why did the tool suggest an unsuitable dish? How could the request have been re-formulated? Such analysis improves AI working skills.
Practice joint use: suggest a friend enter their ingredients and restrictions, then discuss the received recipes. This will add a game element and allow you to see different approaches. Remember, the tool is just an assistant, the final decision is yours.
Exercise: generate a recipe for 4 portions for 45 minutes with the same ingredients. Compare with the previous result for 2 portions for 30 minutes.
The "What to cook" recipe generator is a convenient tool for quickly getting ideas for dishes from available products. It takes as input ingredients, restrictions, number of portions and time, and outputs a text recipe. To use it effectively, formulate requests precisely, check the results against your conditions and take into account restrictions: possible errors, lack of history and integrations. Practice, experiment with formulations, and you will learn to quickly find culinary solutions. Remember, the tool does not replace your culinary experience, it only complements it.
Open tool: Recipe generator ↗Interface translations are machine-assisted and may need refinement.