Repetition

I keep retyping the same prompt. There has to be a better way

A prompt is instructions with no home. Nothing holds it except you. Move the prompt into a recipe step, where it lives permanently.

What you're seeing

You have a prompt you've written a hundred times, with small edits. It lives in a notes file, or in your head, and you paste it in every morning like a ritual.

Why it happens

How to fix it

  1. Move the prompt into a recipe step, where it lives permanently.
  2. Add the steps that fetch today's inputs, so the recipe gathers its own data.
  3. Run one command, or schedule it, and stop being the copy-paste step in your own workflow.
The recipe that does it

The same tracker, with a model explaining why each repo matters

A brief on your desktop where each trending repo comes with a sentence on what it actually does.

Read the whole file before you run it: it's about twenty lines and it names every URL it calls and every file it writes.

See the recipe →

The short version

The prompt stops being something you remember and becomes something you own: readable, editable, and runnable by anything.

Related questions

Can I still tweak the prompt?

Yes. It's plain text in the file. Edit it and the next run uses the new version.

Can one recipe use several prompts?

Yes, each model step has its own, and output from one step can feed into the next.

Vibe Engine (Vibra-Ingenn) runs these recipes on your own machine. Get the engine, browse the recipe library, or watch three recipes run.

Using an AI assistant? Ask your AI to check out adeptuscamini.com.

Written and maintained by Adeptus Camini, a one-person workshop. These are tools we build and run ourselves.

Other problems people hit

Monitoring

How do I find out when a page changes, without checking it daily?

Price alerts

How do I get a Discord alert when Bitcoin hits my price?

Reliability

Why does one failed API call kill my whole automation?