Claude prompt for product photography: Hero Banner (Common Fixes)
Claude · Product Photography · Common Fixes
You are a pragmatic coach using Claude for product photography, specifically hero banner.
Job: wide crop for homepage.
Audience: web teams. Constraint: negative space for type.
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.Looking for a Claude prompt for hero banner? Start here — the common fixes angle focuses on typical failures and how to repair the prompt. In practice, one customization pass is enough when the brief is this specific. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
For Anthropic models, product photography prompts fail when they mix strategy and execution. This hero banner brief separates the job so you can iterate once, not ten times. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Locks the audience (web teams) before style so tone stays honest.
- Forces an output contract: headings, examples, and a final version.
- Keeps product photography vocabulary specific instead of buzzwords.
- Separates draft from critique so you can steal the structure later.
- Uses diagnostic language that matches how practitioners actually brief work.
How to use it in Claude
Save the winning variant for hero banner — teams with a short library ship faster. Redact client names; keep structure. Slug hero-banner-fixes is your canonical URL for this brief. For product photography work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Pack shots, lifestyle scenes, and catalog consistency. Keep that context in the thread when you iterate. When web teams review output, they should see typical failures and how to repair the prompt without hunting for it.
Start with the ugly first pass for hero banner. Name what is wrong in five bullets, then rerun in Claude. For hero banner in product photography, the failure mode is usually no example. This prompt blocks that by design — especially "negative space for type". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for hero banner; they cannot invent metrics or brand rules. brand and ecommerce teams teams bookmark slug hero-banner-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 (web teams, offer, timeline).
- Confirm the constraint is still visible: negative space for type.
- 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 Hero Banner, 3 short sections, bullet list of recommendations, closing line that states negative space for type. Facts you supply appear; nothing invented.
Common mistakes
- Deleting "negative space for type" to save space — that is usually the whole point.
- Accepting the first draft without checking wide crop for homepage.
- Ignoring the output contract headings.
Expert notes
Slug hero-banner-fixes: a brand and ecommerce teams-oriented product photography brief. Pack shots, lifestyle scenes, and catalog consistency. 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 negative space for type no longer matches policy.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a hero banner 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
- web teams should recognize themselves in the first paragraph.
- Product Photography work needs pack shots, lifestyle scenes, and catalog consistency.
- The Common Fixes variant is for typical failures and how to repair the prompt.
- Ship a draft, then tighten. Do not chase a perfect first token.
- Claude improves when you paste a real snippet or reference still.
FAQ
- What is a Claude prompt for hero banner?
- It is a structured brief that tells Claude how to produce product photography output for web teams. This common fixes version stresses typical failures and how to repair the prompt and keeps "negative space for type" in the instructions.
- How do I customize this Claude product photography prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "negative space for type" should stay unless your brief truly changed.
- Why use the common fixes angle for hero banner?
- Different angles solve different failures. Common Fixes helps when web teams 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.