Claude prompt for storytelling: Product Metaphor (Starter)
Claude · Storytelling · Starter
You are a senior specialist using Claude for storytelling, specifically product metaphor.
Job: one extended image.
Audience: explainers. Constraint: know when to stop.
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 product metaphor prompt to ship faster drafts that respect "know when to stop". Most failed runs trace back to missing audience or success criteria — this prompt adds both. 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 product metaphor 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
- Centers one extended image so success is observable.
- Repeats the hard constraint: know when to stop.
- Separates draft from critique so you can steal the structure later.
- Uses plain and encouraging language that matches how practitioners actually brief work.
- Forces an output contract: headings, examples, and a final version.
How to use it in Claude
Arcs, case stories, and audience journeys. Keep that context in the thread when you iterate. Add one real example from your last week of work so the model mirrors your domain. Save the winning variant for product metaphor — teams with a short library ship faster. Redact client names; keep structure. Slug product-metaphor-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 checklist explainers would use. Then grade the draft against one extended image. For product metaphor in storytelling, the failure mode is usually vague audience. This prompt blocks that by design — especially "know when to stop". Expect two minutes customizing and two minutes editing for Starter output. Anthropic models still need your facts for product metaphor; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug product-metaphor-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 (explainers, offer, timeline).
- Confirm the constraint is still visible: know when to stop.
- 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 Product Metaphor, 3 short sections, bullet list of recommendations, closing line that states know when to stop. Facts you supply appear; nothing invented.
Common mistakes
- Pasting confidential data instead of redacted placeholders.
- Accepting the first draft without checking one extended image.
- Ignoring the output contract headings.
Expert notes
Slug product-metaphor-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 know when to stop no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a product metaphor 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
- Storytelling work needs arcs, case stories, and audience journeys.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Keep know when to stop visible in the prompt, not only in your head.
- State the job (one extended image) in one line before any style talk.
- If text output drifts, re-anchor with know when to stop.
FAQ
- What is a Claude prompt for product metaphor?
- It is a structured brief that tells Claude how to produce storytelling output for explainers. This starter version stresses first successful run with safe defaults and keeps "know when to stop" 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 "know when to stop" should stay unless your brief truly changed.
- Why use the starter angle for product metaphor?
- Different angles solve different failures. Starter helps when explainers 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.