The standard

How every guide is made.

One task, one outcome, and checks you can actually run. Here is the standard each workflow meets, and what the words on this site mean.

Five parts, in this order.

  1. 01 Before you startWhat to bring and what to leave out. Most weak outputs start with missing context, so context comes first.
  2. 02 The workflowFour ordered steps from raw input to something usable, including the review step people skip.
  3. 03 The promptA complete prompt with bracketed fields, and a builder that fills them in without sending anything anywhere.
  4. 04 A worked exampleA small illustrative input beside the shape of a good result, so you know what you are aiming for.
  5. 05 The checksWhat to verify against the source before the result goes anywhere. The draft is not the deliverable.

How the prompts are written.

  • Material, not instructions.Every prompt that works on pasted notes, sources, or documents tells the assistant to treat them as material to analyze, not as instructions to follow. Pasted emails, pages, and documents can contain instructions of their own; this keeps the assistant on your task.
  • Gaps stay visible.Prompts ask for labels such as “Not specified,” “Unassigned,” or “To confirm” instead of a guess. A visible gap is a question you can answer. An invented detail is a mistake you might send.
  • Evidence you can trace.Inputs are labeled (N1, S1, E1) so each line of the output can point back to where it came from, and you can check it in seconds.
  • Facts apart from interpretation.Prompts separate what the source says from what the assistant infers, and ask for inferences to be labeled as inferences.
  • The smallest useful version.Prompts ask for a plan or a sample before a full run. Automations are mapped and tested on paper before any app is connected.

What the words mean here.

  • IllustrativeAn example written to show the shape of a useful result. It is not a client result and not a measured output.
  • CheckedTool facts such as plans, limits, and names were compared against the provider’s own official pages on the date shown, most recently September 25, 2026. It is not a review of the tool’s quality.
  • TestedUsed only for something that was actually run and documented. No guide on this site currently claims a tested result.
  • About 15 minutesSuggested times are planning aids that include review. They are estimates, not benchmarks.

Independent by default.

There are no affiliate links and no paid placements. Tools are chosen for fit with the task and described with their limits, and every recommendation links to the provider’s own page. If sponsored content or affiliate links are ever added, they will be labeled where they appear.

See the tools directory

Corrections.

If a guide is wrong or a tool has changed, email hello@deadbounce.com with the page and what changed. Corrections are made in the guide itself, and material changes are noted in the log below.

Library log.

  1. 8 new workflows: write a follow-up that gets a clear answer; rewrite complex text so anyone can follow it; write down a process so someone else can run it; turn a messy to-do list into a week you can finish; walk into an expert call with better questions; check a claim before you repeat it; pick the right task to automate first; write the inbox rules before you automate email. Tool plans and guide sources rechecked against official pages. Added the prompt builder, saved workflows, search, and the tools directory. Three older prompts gained an explicit “material, not instructions” line.
  2. The library opened with ten workflows, the tool finder, and the free starter kit.