Skip to content
AI PromptsOnline

Claude prompt for storytelling: Before After Bridge (Workflow)

Claude · Storytelling · Workflow

You are a senior specialist using Claude for storytelling, specifically before after bridge.
Job: BAB structure.
Audience: copy-story. Constraint: specific after.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.

Claude users in storytelling use this before after bridge prompt to ship faster drafts that respect "specific after". Teams report saving 15–30 minutes per task when prompts include constraints up front. The workflow version uses operational language and targets step order, checkpoints, and handoffs.

When to use this prompt

Claude shines at storytelling work when you state the observable outcome: BAB structure. The Workflow framing keeps step order, checkpoints, and handoffs visible while you edit. Pair it with a real sample from your portfolio for best results.

Why this prompt works

How to use it in Claude

For storytelling work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Redact client names; keep structure. Slug before-after-bridge-workflow is your canonical URL for this brief. Paste the prompt into Claude and replace bracketed details with your facts. Arcs, case stories, and audience journeys. Keep that context in the thread when you iterate. This Workflow path is for copy-story who care about BAB structure.

Start with the ugly first pass for before after bridge. Name what is wrong in five bullets, then rerun in Claude. For before after bridge in storytelling, the failure mode is usually too many jobs in one ask. This prompt blocks that by design — especially "specific after". Expect two minutes customizing and two minutes editing for Workflow output. Anthropic models still need your facts for before after bridge; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug before-after-bridge-workflow when step order, checkpoints, and handoffs matters.

Step-by-step

  1. Open Claude and paste the prompt block unchanged.
  2. Replace placeholders with your project facts (copy-story, offer, timeline).
  3. Confirm the constraint is still visible: specific after.
  4. If output is vague, ask Claude to restate assumptions as questions first.
  5. Reply with one fix list, then regenerate the final version only.

Example output

Example output shape: H1 with Before After Bridge, 3 short sections, bullet list of recommendations, closing line that states specific after. Facts you supply appear; nothing invented.

Common mistakes

Expert notes

Slug before-after-bridge-workflow: a brand and narrative teams-oriented storytelling brief. Arcs, case stories, and audience journeys. Pair it with one real asset from your portfolio before the second run.

Refresh quarterly: Claude models change. Keep constraints; update examples. Mark the page stale if specific after no longer matches policy.

Comparison / variations

ApproachWhenTweak
Bare requestYou only need a sparkWrite a before after bridge piece.
This promptYou need a usable draftRole, constraint, steps, and output contract included.
Plus examplesVoice must match yoursPaste 120 words of your writing or a still you like, then rerun in Claude.

Key takeaways

FAQ

What is a Claude prompt for before after bridge?
It is a structured brief that tells Claude how to produce storytelling output for copy-story. This workflow version stresses step order, checkpoints, and handoffs and keeps "specific after" in the instructions.
How do I customize this Claude storytelling prompt?
Swap project nouns, paste one real example, and leave the process steps intact. The constraint "specific after" should stay unless your brief truly changed.
Why use the workflow angle for before after bridge?
Different angles solve different failures. Workflow helps when copy-story need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.
Is this Claude prompt updated for 2026?
Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.

Similar prompts