Claude prompt for storytelling: Community Lore (High Converting)
Claude · Storytelling · High Converting
You are a systems thinker using Claude for storytelling, specifically community lore.
Job: shared history.
Audience: fandom. Constraint: inclusive.
Working style: outcome-led. Optimize for clarity, specificity, and measurable results.
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.This Claude storytelling community lore prompt helps you shared history without rewriting instructions from scratch each time. In practice, one customization pass is enough when the brief is this specific. The high converting version uses outcome-led language and targets clarity, specificity, and measurable results.
When to use this prompt
Claude shines at storytelling work when you state the observable outcome: shared history. The High Converting framing keeps clarity, specificity, and measurable results visible while you edit. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Locks the audience (fandom) before style so tone stays honest.
- Centers shared history so success is observable.
- The high converting angle adds clarity, specificity, and measurable results without extra fluff.
- Keeps storytelling vocabulary specific instead of buzzwords.
- Repeats the hard constraint: inclusive.
How to use it in Claude
Use outcome-led follow-ups only — mixing tones mid-thread confuses Anthropic models. Name the success metric aloud: shared history. If the draft cannot pass it, do not polish prose yet. When fandom review output, they should see clarity, specificity, and measurable results without hunting for it. Save the winning variant for community lore — teams with a short library ship faster. Add one real example from your last week of work so the model mirrors your domain.
Swap the audience once. If the community lore piece still works, the core is solid. For community lore in storytelling, the failure mode is usually vague audience. This prompt blocks that by design — especially "inclusive". Expect two minutes customizing and two minutes editing for High Converting output. Anthropic models still need your facts for community lore; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug community-lore-high-converting when clarity, specificity, and measurable results matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (fandom, offer, timeline).
- Confirm the constraint is still visible: inclusive.
- Add a 100-word example before the second run if voice matters.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Community Lore, 3 short sections, bullet list of recommendations, closing line that states inclusive. Facts you supply appear; nothing invented.
Common mistakes
- Skipping the audience (fandom) and hoping Claude infers it.
- Using the High Converting prompt but editing it into a vague one-liner.
- Asking for community lore plus three other jobs in one message.
Expert notes
This Claude page targets "shared history" for fandom. Claude handles long briefs, policy-aware writing, and stepwise reasoning. The outcome-led tone keeps clarity, specificity, and measurable results visible while you edit.
Workflow tip: save three winning outputs for community lore and diff them. The shared skeleton becomes your team standard inside Claude.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a community lore 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
- The High Converting variant is for clarity, specificity, and measurable results.
- Storytelling work needs arcs, case stories, and audience journeys.
- State the job (shared history) in one line before any style talk.
- Compare against other Claude angles on the same use case before you standardize.
- Document what changed when you customized slug community-lore-high-converting.
FAQ
- What is a Claude prompt for community lore?
- It is a structured brief that tells Claude how to produce storytelling output for fandom. This high converting version stresses clarity, specificity, and measurable results and keeps "inclusive" 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 "inclusive" should stay unless your brief truly changed.
- Why use the high converting angle for community lore?
- Different angles solve different failures. High Converting helps when fandom need clarity, specificity, and measurable results. 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.