Claude prompt for storytelling: Before After Bridge (Starter)
Claude · Storytelling · Starter
You are a senior specialist using Claude for storytelling, specifically before after bridge.
Job: BAB structure.
Audience: copy-story. Constraint: specific after.
Working style: plain and encouraging. Optimize for first successful run with safe defaults.
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.A Claude prompt for storytelling is a copy-ready brief for before after bridge aimed at copy-story. In practice, one customization pass is enough when the brief is this specific. The starter version uses plain and encouraging language and targets first successful run with safe defaults.
When to use this prompt
Claude shines at storytelling work when you state the observable outcome: BAB structure. The Starter framing keeps first successful run with safe defaults visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Uses plain and encouraging language that matches how practitioners actually brief work.
- Repeats the hard constraint: specific after.
- Asks for a self-check pass, which cuts hallucinated details.
- Centers BAB structure so success is observable.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Ask for a shorter version after the long one; compression reveals weak claims. Add one real example from your last week of work so the model mirrors your domain. Arcs, case stories, and audience journeys. Keep that context in the thread when you iterate. If the first answer is vague, reply with the constraint again: specific after. For storytelling work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt.
Have Claude list assumptions about storytelling before drafting. Delete any you cannot defend. 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 Starter 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-starter when first successful run with safe defaults matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (copy-story, offer, timeline).
- Confirm the constraint is still visible: specific after.
- If output is vague, ask Claude to restate assumptions as questions first.
- 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
- Accepting the first draft without checking BAB structure.
- Using the Starter prompt but editing it into a vague one-liner.
- Skipping the audience (copy-story) and hoping Claude infers it.
Expert notes
Anthropic users working on before after bridge in storytelling should treat "specific after" as non-negotiable. Arcs, case stories, and audience journeys. When copy-story run the Starter variant, they usually care about first successful run with safe defaults more than length.
If text output feels generic, re-paste specific after as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a before after bridge piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Keep specific after visible in the prompt, not only in your head.
- State the job (BAB structure) in one line before any style talk.
- Storytelling work needs arcs, case stories, and audience journeys.
- Compare against other Claude angles on the same use case before you standardize.
- Claude improves when you paste a real snippet or reference still.
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 starter version stresses first successful run with safe defaults 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 starter angle for before after bridge?
- Different angles solve different failures. Starter helps when copy-story need first successful run with safe defaults. 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.