Turn a repeated task into your own recipe

CRAFT Tutorials · Advanced

If you find yourself explaining the same multi-step task to Claude again and again, you can capture it once as your own reusable recipe — then run it any time by name, no re-explaining. CRAFT writes it up for you; you just describe what you want.

What a recipe is — and why make your own

A recipe is a saved set of steps Claude can run on request. CRAFT comes with a library of built-in recipes, but the real power is making your own: any task you do more than a couple of times — a weekly report, a way you like files named, a checklist you run before sharing work — can become a one-line command.

  • Stop repeating yourself. Describe the task once; reuse it forever.
  • Stay consistent. The steps run the same way every time.
  • It’s yours. Your recipes are personal — saved in your own project, kept separate from the built-in ones.

Step 1 — Do the task once

The easiest way to make a good recipe is to walk through the task with Claude as you normally would — getting the steps and the result the way you like them. A recipe built from a real run captures what actually works.

Step 2 — Ask Claude to save it as a recipe

Once you’re happy with how it went, turn it into a recipe and give it a name:

›Turn what we just did into a reusable recipe called “weekly sales summary.”

Claude writes it up as a proper CRAFT recipe — in your own personal space, not mixed in with the built-in ones — and gives it a trigger phrase so you can call it later. If you’re starting from scratch instead of a run you just did, that’s fine too; just describe the steps:

›Make me a recipe called “tidy downloads” that sorts my new files into folders by type and date.

✓ You’ll know it worked when Claude confirms your recipe is saved and tells you the phrase that runs it.

Step 3 — Run it any time

From now on, you don’t re-explain a thing — you just ask for it by name:

›Run my “weekly sales summary” recipe.

✓ You’ll know it worked when Claude runs your saved steps and produces the same kind of result as the first time.

Good to know: your recipes live in your project alongside your work, so they travel with it — including to GitHub and any other computer you’ve set up. They’re entirely yours; making one never changes CRAFT’s built-in recipes.

Troubleshooting

  • You forgot a recipe’s name — ask Claude to “list my recipes.”
  • The recipe needs a tweak — just ask Claude to edit it (for example, “update my ‘tidy downloads’ recipe to also handle screenshots”).
  • You want it to run differently each time — recipes can take details you supply when you run them; tell Claude what should be flexible and it’ll build that in.

That’s your first recipe: do it once, save it, run it by name forever. A good next step: Chain recipes into a multi-step workflow — combine several recipes into one command.

Similar Posts