Saving recipes from ChatGPT is easy; cooking them twice is the hard part. A month of enthusiastic saving produces forty thoughts with titles like “Dinner recipe” and “Pasta idea 2”, and you go back to the same three meals you always make. This guide is the organisation layer: title conventions that make search work, when to split projects (and when not to), how to keep shopping lists from polluting the cookbook, and the two-minute annotation that turns a generated recipe into yours.

Start with one Recipes project. Stay longer than you expect.

The instinct to create Baking, Italian, Slow Cooker and Weeknight projects on day one feels organised and ages badly. A recipe can only sit in one project, but it can be weeknight and Italian and vegetarian — categories overlap, projects do not. One Recipes project plus good titles and search beats a taxonomy you must adjudicate for every save. This is the same restraint recommended for notes generally in organising notes by project: split only when browsing genuinely gets slow or the sharing audience differs.

There are two honourable exceptions. A shared household cookbook and a private experiments project have different audiences, so they deserve separate projects from the start. And if you bake weekly, a Baking project you browse with floury hands earns its independence. Let use, not symmetry, decide.

Titles do the finding

Search in Thoughts matches the words in titles, text and tags, so the title is your retrieval system. A reliable pattern:

Dish — the thing that distinguishes this version

  • “Mushroom risotto — weeknight, for two”
  • “Mushroom risotto — pressure cooker, for four”
  • “Tomato soup — roast first, freezes well”
  • “Chicken marinade — yoghurt and harissa, overnight”

Put the searchable noun first (“risotto”, not “easy creamy…”), and spend the tail on the detail future-you will type: equipment, servings, speed, freezer-friendliness. When your assistant saves a recipe, dictate the title in the same breath: “save it as ‘Lentil soup — stovetop, batch of six’”. The save workflow is in saving recipes from ChatGPT; this naming habit is what makes every later step work.

Keep lists and plans visibly temporary

Grocery lists and week plans live happily in the same project if their titles announce their lifespan. Prefix lists with “Shop:” plus a date (“Shop: week of 20 Oct”), and title plans “Week of 20 Oct — dinners”. Browsing Recipes then reads as a cookbook with a few dated documents at the front, and deleting an old list never risks deleting a keeper. More on generating both in grocery lists and weekly meal plans.

Annotate after cooking — two minutes, while it is true

Generated recipes arrive generic. They become yours in the margins. After cooking, open the thought in Thoughts and add what the recipe did not know: “our oven needs +10 minutes”, “halve the chilli for the kids”, “sauce is thin — reduce it next time”, “doubled for six, worked”. Date it if you like. This is the highest-value habit in this guide, for two reasons: you will trust and reuse annotated recipes, and your assistant reads those annotations when you later ask it to adapt the dish or plan a week around it.

Voice capture makes this painless with wet hands: dictate the note, let on-device tidying clean it up, done. The capture-review-file loop from turning voice notes into organised notes is the same move in a kitchen context.

Variations get their own thoughts; originals stay canonical

When you ask ChatGPT or Claude to adapt a saved recipe — different servings, pressure cooker, vegan — save the result as a new thought with its distinguishing title, and leave the original alone. The connector cannot edit your existing thoughts anyway; that limitation is a feature here, because it preserves a trusted base with honest descendants, the way paper cookbooks accumulate. Cook a variation twice and prefer it? Rename titles so the favourite is obvious, or note “superseded by pressure-cooker version” at the top of the old one.

A monthly five-minute tidy

Once a month, scroll Recipes with a cup of tea. Delete lists older than the month. Rename anything vague you stumble on (“Pasta thing” — you know the one). Merge nothing; delete duplicates only when one is clearly the annotated keeper. If the scroll has become genuinely long, now is the moment a Baking or Batch split has earned itself. Five minutes keeps the shelf a cookbook rather than an archive — the same small-review philosophy as the weekly review, at cookbook scale.

The test of the system is a tired Tuesday: open Thoughts, search “soup”, “weeknight” or “freezes”, and be cooking inside a minute. If that works, your organisation is done — however few projects it uses.

Frequently asked questions

How many recipe projects should I have in Thoughts?

Start with one Recipes project and rely on titles and search. Split only when browsing gets slow or audiences differ, such as a shared household cookbook versus private experiments, or a Baking project you use weekly.

What is a good title format for a saved recipe?

Dish first, then the distinguishing detail: for example Mushroom risotto — pressure cooker, for four. Put the searchable noun up front and spend the rest on equipment, servings, speed or freezer notes you will actually search for.

Where do grocery lists and meal plans belong?

In the same Recipes project, with dated, prefixed titles such as Shop: week of 20 Oct. They stay visibly temporary, so you can delete them later without risking keeper recipes.

How do I turn a generated recipe into one I trust?

Annotate the thought in Thoughts right after cooking: timing tweaks for your oven, seasoning changes, scaling notes. Two minutes of honest margin notes makes the recipe reusable, and your assistant reads them when adapting it later.