Most of us learned to cook forwards: find a recipe, buy its ingredients, follow the steps. It works beautifully, exactly once. Then you’re left holding the recipe’s exhaust — half a bunch of cilantro, two-thirds of a can of coconut milk, a knob of ginger with one ambition left in it — and the next recipe you pick will need none of those things.
Do this twice a week for a month and your fridge becomes a museum of other dinners’ leftovers. Nothing in it goes together, because nothing in it was ever meant to. You bought components, not a kitchen.
The fix isn’t better recipes. It’s reversing the direction of the question.
Restaurants already cook backwards
Here’s the thing nobody tells you about the “chef’s special”: it’s rarely inspiration. It’s inventory. The fish special exists because there is fish, and the fish will not survive until Thursday. The soup of the day is yesterday’s vegetables wearing a new name.
That’s not cynicism — it’s the entire skill. A professional kitchen looks at what it has, what’s closest to the edge, and what the stove can do in the time available, and then decides what dinner is. The menu bends around the inventory, not the other way round.
Home cooking teaches the opposite reflex. We decide what we want to eat — usually while nowhere near the kitchen — and then go buy it, stepping over the perfectly good food we already own on the way out the door.
The five templates
Cooking backwards needs a different tool than a recipe: a template. A template is a dish that keeps its shape no matter what you pour into it. Five of them cover almost any fridge state we’ve ever faced.
Fried rice. The most forgiving dish on earth. Needs day-old rice, an egg if you have one, and literally any vegetable, cooked meat, or sad half-onion in the crisper. Soy sauce and heat do the rest. If your rice is fresh, spread it on a plate and give it ten minutes — drier is better.
Frittata. Eggs turn odds and ends into a meal with a name. Roasted vegetables from Tuesday, the last inch of feta, wilting herbs, that single cooked potato. Whisk, pour, low heat, lid on. It’s quiche for people who don’t want to negotiate with pastry.
Soup. An onion, a fat, and anything else. Vegetables past their crunch make better soup than fresh ones — softness stops being a flaw and starts being the point. Blend it and nobody can even reconstruct the evidence.
The grain bowl. Cook a pot of anything (rice, bulgur, couscous), then raid: something roasted, something raw, something pickled, something creamy, something crunchy. It isn’t a recipe, it’s an assembly rule.
Pasta, aglio-olio-plus. Garlic, olive oil, pasta water — that’s the engine. The “plus” is whatever needs to go: capers, that lonely tomato, the parmesan heel, half a jar of olives, a handful of spinach that has maybe a day left.
None of these care what you have. They only care that you have something.
Check the axes, not the recipe
The reason template dinners sometimes taste like a compromise is not the ingredients — it’s balance. Before it hits the table, run it against five axes:
- Salt — almost every bland dinner is an under-salted dinner.
- Fat — a last-minute knob of butter or thread of olive oil.
- Acid — lemon, vinegar, pickle brine. The one home cooks skip most.
- Heat — chili flakes, black pepper, a spoon of chili crisp.
- Crunch — toasted nuts, breadcrumbs, raw onion. Texture is seasoning.
A fried rice that tastes flat almost never needs another ingredient. It needs acid and crunch. This checklist is cheaper than a shopping trip.
When you should still use a recipe
Cooking backwards is a weeknight skill, not a religion. Recipes still win in three places: baking, where ratios are chemistry and improvising is how you invent a cracker; cuisines you don’t know yet, where the recipe is a teacher, not a shopping list; and cooking for guests, when you want the outcome guaranteed.
The trick is to notice what a recipe is for. The first time, it teaches you a pattern. The fifth time, the pattern belongs to you — and patterns, unlike recipes, don’t generate orphan ingredients.
The question that changes the week
Forward cooking asks: what do I want to eat? — a question with infinite answers, none of which are in your kitchen.
Backward cooking asks: what wants to be eaten? — a question your fridge can answer in about fifteen seconds, especially if you keep a rough audit habit going.
Ask it before you ask anything else. Most nights, dinner was already home.
Cooking backwards has exactly one prerequisite: knowing what’s in there. A list on the fridge door does it. So does shElf, which we’re building to do the looking for you — it ranks what you can cook against what’s actually on your shelves and what’s closest to going off. The templates above are the part that works tonight, with no app at all.
