Skip to main content
A prompt that works is a recipe, not a scrap of paper. A recipe you’ll cook again goes in a binder; a recipe you use once goes in the trash. The only difference between “a prompt I happened to type” and “a reusable asset” is whether you deliberately kept it. This page is about keeping the wins — capturing them once and reusing them forever, instead of scrolling old chats to find the phrasing that landed last time. The loop: recognize → capture → generalize → chain into a workflow → share.

​
Step 1 — Recognize a repeat task

Three signals tell you a task is worth saving:
  • You’ve typed something very similar before.
  • You catch yourself scrolling old chats to copy-paste a prompt.
  • The task recurs on a cadence — weekly, per-deal, per-document.
Common examples: the weekly status summary you send your manager, or the standard checklist you run over every incoming contract.

​
Step 2 — Capture the prompt that worked

Save it right after a good result — not from memory later, when you’ve forgotten the exact wording that landed. Save the actual prompt text, not just the output. There are two flavors of library:
  • Personal — just for your own recurring tasks.
  • Team — for things your whole team repeats.

​
What makes a prompt library-worthy

Reuse only pays off if the prompt was built well. Generalize the parts that don’t change — the role, the standard, the output format — and clearly mark the part that does — the input — so future-you can drop in new details fast.
Write a recurring prompt with an explicit input slot, e.g. a [paste this week's updates] placeholder, instead of hardcoding the current week’s content. Same ask, same standard, same format — only the input changes.

​
Step 3 — Turn a multi-step task into a workflow

A prompt is one ask. A workflow is a chained sequence: pull the source material → apply the standard → flag exceptions → produce the final format. For example, a document-review workflow: open the doc, run it against the review checklist, flag anything that deviates, and summarize the flags. Once you’ve proven that sequence by hand, it’s a candidate to save as one rerunnable workflow — and, per the Features deep dive, potentially a scheduled job later.

​
Step 4 — Share it with your team

A prompt saved only to you helps only you. The payoff multiplies the moment a teammate doing the same recurring task finds your saved prompt instead of reinventing it.
Name it so someone else can find and understand it at a glance — “Weekly team status summary,” not “prompt3.”

​
Beyond your library: group & admin-shared assets

Peer-to-peer sharing is one tier. Above it, an admin can provision an agent or skill for a whole group — for example, a “paralegal ops” group with a shared contract-reviewer agent everyone uses. The key payoff is that a group asset is centrally maintained: when the owner improves it and saves, everyone in the group gets the newest version automatically — no re-sharing files, no version drift, no “which copy is current?” To get a group asset, ask your admin or the Aperium team.

​
Pitfalls

  • Too specific. A prompt hardcoded to one week’s numbers is dead weight next time — generalize the variable parts.
  • Gone stale. A saved prompt can drift if the system or process it references changes. Treat your library like a garden, not a vault — prune and update it occasionally.
  • Over-engineered. Don’t build a whole saved workflow for a task you’ll genuinely only ever do once.