Claude prompt for storytelling: Origin Story (Starter)
Claude · Storytelling · Starter
You are a systems thinker using Claude for storytelling, specifically origin story.
Job: why this exists.
Audience: founders. Constraint: scene not resume.
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.Claude users in storytelling use this origin story prompt to ship faster drafts that respect "scene not resume". 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
For Anthropic models, storytelling prompts fail when they mix strategy and execution. This origin story brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Names a clear job so Claude does not wander into generic advice.
- Forces an output contract: headings, examples, and a final version.
- Separates draft from critique so you can steal the structure later.
- Asks for a self-check pass, which cuts hallucinated details.
- Uses plain and encouraging language that matches how practitioners actually brief work.
How to use it in Claude
Redact client names; keep structure. Slug origin-story-starter is your canonical URL for this brief. Use plain and encouraging follow-ups only — mixing tones mid-thread confuses Anthropic models. Ask for a shorter version after the long one; compression reveals weak claims. When founders review output, they should see first successful run with safe defaults without hunting for it. Name the success metric aloud: why this exists. If the draft cannot pass it, do not polish prose yet.
Run a constrained version and a wild version of origin story. Keep structure from one and energy from the other. For origin story in storytelling, the failure mode is usually missing constraint. This prompt blocks that by design — especially "scene not resume". Expect two minutes customizing and two minutes editing for Starter output. Anthropic models still need your facts for origin story; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug origin-story-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 (founders, offer, timeline).
- Confirm the constraint is still visible: scene not resume.
- 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 Origin Story, 3 short sections, bullet list of recommendations, closing line that states scene not resume. Facts you supply appear; nothing invented.
Common mistakes
- Asking for origin story plus three other jobs in one message.
- Using the Starter prompt but editing it into a vague one-liner.
- Deleting "scene not resume" to save space — that is usually the whole point.
Expert notes
Slug origin-story-starter: 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 scene not resume no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a origin story 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 scene not resume visible in the prompt, not only in your head.
- Storytelling work needs arcs, case stories, and audience journeys.
- The Starter variant is for first successful run with safe defaults.
- Ship a draft, then tighten. Do not chase a perfect first token.
- If text output drifts, re-anchor with scene not resume.
FAQ
- What is a Claude prompt for origin story?
- It is a structured brief that tells Claude how to produce storytelling output for founders. This starter version stresses first successful run with safe defaults and keeps "scene not resume" 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 "scene not resume" should stay unless your brief truly changed.
- Why use the starter angle for origin story?
- Different angles solve different failures. Starter helps when founders 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.