What you’ll take away
- Save repeatable task rules and keep changing inputs explicit.
- Separate client preferences from project-specific source facts.
- Use different instructions when the delivery changes, even for the same client.
Decide what you are trying to remember
Recurring instructions often mix several things: preferred caption layout, file naming, delivery dimensions, the client's audience, and the details of the current story. Only some remain stable. A source filename, speaker name, or campaign message should not be carried into the next job by accident.
For an illustrative two-client setup, one client wants restrained captions for a website interview and another needs a different treatment for short social clips. The reusable task can ask which client and delivery apply, then use the selected preferences. It should not guess from a folder name that happens to resemble an earlier project.
Choose a skill for one recurring job
Wideframe's build-a-skill page describes clarifying a single task, checking its feasibility, and saving reusable instructions. Begin there when you have a repeated job such as preparing captions or applying a consistent source-note format.
For the two-client caption example, use Caption This as the starting recipe. Add and save it in a blank Wideframe chat, then adapt its delivery and readability instructions into the client-specific task. Include a client-and-cut confirmation in the saved instructions, then supply those details when you invoke the task. Its defaults are a starting point, not automatic knowledge of either brand, and dialogue captions remain separate from identity graphics.
Copy the public recipe into a new Wideframe chat and explain the task you repeat. Keep the first version small. A skill that tries to interpret the brand, assemble the whole story, finish the graphics, and decide approval is harder to maintain than one that handles a defined production step.
Give the workflow explicit changing inputs
Tell it what must be confirmed on every run: client, source folder or sequence, delivery type, output location, and any current exceptions. Fixed rules can then remain in the reusable instructions. This avoids repeatedly writing the same paragraph while keeping important choices visible.
For a caption task, the fixed rules may define how identity text and subtitles are separated. The changing inputs include the current video, names, and destination. Do not treat a successful result on one sentence as evidence that every future name or technical phrase is already known.
Keep the client brief readable by people too
Store the core preferences in a form a producer or editor can understand. A short task description with concrete rules is easier to update than a long conversation history. Explain the reason for a rule when that helps someone decide whether an exception is appropriate.
Avoid encoding a subjective preference as a universal numerical command. “Do not rush a complete customer answer” may be a useful editorial intention, while a fixed pause limit may be inappropriate for some speakers. Keep the editor responsible for choices that depend on the actual performance.
Make changes to the brief deliberate
When a client changes its style or delivery requirements, update the relevant saved task and identify the revision. Do not assume an instruction in one unrelated chat has changed every future run. Keep the new requirement close to the workflow it affects.
If a one-off campaign departs from the usual style, state the exception in that project's brief. Do not rewrite the client's recurring defaults unless the change is meant to persist. This is particularly useful for agencies moving between clients on the same day.
Start the next project with context, not a blank command
Identify the current source and invoke the saved task by its established name or a clear description. State which client preferences apply and any exceptions. The assistant should have enough information to act without importing source details from another job.
Open the resulting work in the normal finishing environment and make the necessary editorial adjustments. A reusable workflow reduces repeated instruction; it does not remove responsibility for the current deliverable. Keep useful improvements to the task and leave one-off creative choices in the project.
Choose reuse when the task actually recurs
If every project asks for a different creative outcome, a fresh brief may be the better tool. Save instructions when the production task has stable choices and occurs often enough to justify maintenance. The benefit is clearer repeated work, not a claim that the assistant has learned the entire client relationship.
For teams producing recurring interviews or customer stories, caption preparation, source-note conventions, and explicit review-note handling are useful starting points. Each has a tangible output and a reason to run again on the next piece of footage.
Try this request
Help me save a reusable caption-preparation task for these client preferences. Ask for the client, current sequence, destination, and exceptions each time. Keep source names and project-specific claims out of the saved defaults.
Sources
Published by Wideframe. Product details are based on the documentation below; examples are not customer results or benchmarks.
- Wideframe build-a-skill workflow · consulted 2026-09-18
- Wideframe: captions · consulted 2026-09-18
- Wideframe caption-this recipe · consulted 2026-09-18
Save the client instructions that repeat
Choose one recurring client task and use Wideframe's skill-building route to save its stable rules while keeping current project inputs explicit.
Frequently asked questions
Do not depend on that. Identify the client and current task explicitly, and use saved instructions for the stable preferences.
Start with one task and the rules relevant to it. Broad creative direction belongs in a readable current brief as well.
Update the relevant saved workflow deliberately and distinguish permanent changes from one-project exceptions.