Claude prompt for storytelling: Origin Story (Advanced)
Claude · Storytelling · Advanced
You are a systems thinker using Claude for storytelling, specifically origin story.
Job: why this exists.
Audience: founders. Constraint: scene not resume.
Working style: precise and demanding. Optimize for constraints, evaluation, and edge cases.
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 strong Claude storytelling origin story prompt names the job, audience, and finish line. This page does that for founders. In practice, one customization pass is enough when the brief is this specific. The advanced version uses precise and demanding language and targets constraints, evaluation, and edge cases.
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
- The advanced angle adds constraints, evaluation, and edge cases without extra fluff.
- Repeats the hard constraint: scene not resume.
- Centers why this exists so success is observable.
- Separates draft from critique so you can steal the structure later.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Use precise and demanding follow-ups only — mixing tones mid-thread confuses Anthropic models. If the first answer is vague, reply with the constraint again: scene not resume. Ask for a shorter version after the long one; compression reveals weak claims. For storytelling work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Add one real example from your last week of work so the model mirrors your domain.
Ask for a checklist founders would use. Then grade the draft against why this exists. 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 Advanced 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-advanced when constraints, evaluation, and edge cases 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.
- For storytelling work, paste a rubric and ask for a self-score.
- 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 Advanced prompt but editing it into a vague one-liner.
- Deleting "scene not resume" to save space — that is usually the whole point.
Expert notes
Practitioners choose Advanced when origin story needs constraints, evaluation, and edge cases. Claude from Anthropic still needs your facts — especially for scene not resume.
For storytelling, compare this Advanced prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on why this exists.
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
- Ship a draft, then tighten. Do not chase a perfect first token.
- Keep scene not resume visible in the prompt, not only in your head.
- State the job (why this exists) in one line before any style talk.
- Document what changed when you customized slug origin-story-advanced.
- Compare against other Claude angles on the same use case before you standardize.
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 advanced version stresses constraints, evaluation, and edge cases 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 advanced angle for origin story?
- Different angles solve different failures. Advanced helps when founders need constraints, evaluation, and edge cases. 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.