Claude prompt for storytelling: Before After Bridge (Common Fixes)
Claude · Storytelling · Common Fixes
You are a senior specialist using Claude for storytelling, specifically before after bridge.
Job: BAB structure.
Audience: copy-story. Constraint: specific after.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
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 common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Claude shines at storytelling work when you state the observable outcome: BAB structure. The Common Fixes framing keeps typical failures and how to repair the prompt visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Centers BAB structure so success is observable.
- Locks the audience (copy-story) before style so tone stays honest.
- Forces an output contract: headings, examples, and a final version.
- Asks for a self-check pass, which cuts hallucinated details.
- Keeps storytelling vocabulary specific instead of buzzwords.
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. Save the winning variant for before after bridge — teams with a short library ship faster. Redact client names; keep structure. Slug before-after-bridge-fixes is your canonical URL for this brief. Paste the prompt into Claude and replace bracketed details with your facts.
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 Common Fixes 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-fixes when typical failures and how to repair the prompt 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 Common Fixes 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 Common Fixes variant, they usually care about typical failures and how to repair the prompt 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
- If text output drifts, re-anchor with specific after.
- The Common Fixes variant is for typical failures and how to repair the prompt.
- Document what changed when you customized slug before-after-bridge-fixes.
- State the job (BAB structure) in one line before any style talk.
- Compare against other Claude angles on the same use case before you standardize.
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 common fixes version stresses typical failures and how to repair the prompt 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 common fixes angle for before after bridge?
- Different angles solve different failures. Common Fixes helps when copy-story need typical failures and how to repair the prompt. 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.