Cost
Retyping a long setup, or attaching the same file again, repeats work.
Home · Start here · 06 · A repeatable workflow
Lesson 6 of 7. Next: When not to use AI.
Lesson · No account
From one chat to a workflow you can repeat
A repeatable workflow keeps the instructions you would otherwise retype: the role, the format, and what to leave out.
1 What it is
A one-off chat holds that setup inside one thread. The thread is easy to lose, and a new chat does not have it. Saved instructions, a project, or a prompt you keep in your own notes carry the parts that should stay the same.
Product names for those features differ and change. This card does not give a click-path. The split is the same everywhere: stable instructions in one place, the new material each time.
Example saved prompt · not a product setting
Stable. Rewrite for a busy reader. Short sentences. Do not add facts. If a number is missing, write "not in the source".
New each time. The paragraph to rewrite.
2 Why it matters
Quality
The version you saved is the one you already corrected. A fresh chat drifts.
Risk
A saved prompt that includes a real customer's data keeps that data in the product. Save the pattern, not the private example.
3 How to apply · try today
Take one prompt you send more than once. Put the stable lines in the product's saved instructions, a project, or a note you control. Next time, add only the new material.
Common mistake
Saving a whole transcript, private details included, and calling it a template.
Self-check
What belongs in the saved part?
Find a prompt you have typed more than once. Split it into two blocks: lines that never change, and the slot for the new material. Save the stable block in the product, or in a note you control. Use it once with new material that has names removed.
Anthropic's context windows guide is about what one request can hold. The same split matters in a chat product: what you put in every time, and what you add only for this task. Idaho's AI guideline says to keep a library of prompts that work for tasks you repeat. The Context engineering card is that decision for a product you are building.
When you are building your own, a Playbook is the how-to for that build. The Examples page shows one build end to end.
Go further
The Context engineering card is deciding what goes into the request this time, and what stays out.
Questions
- Do I need a specific product feature?
- No. A note you control is enough. Use saved instructions or a project if the product you already use has them.
- Can I save the whole chat?
- Only if it has no private details and no reply you have not checked. Otherwise save the instruction, not the transcript.