Claude prompt for product photography: Hero Banner (Starter)
Claude · Product Photography · Starter
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: 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.This Claude product photography hero banner prompt helps you wide crop for homepage without rewriting instructions from scratch each time. 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, 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
- Forces an output contract: headings, examples, and a final version.
- Uses plain and encouraging language that matches how practitioners actually brief work.
- Locks the audience (web teams) before style so tone stays honest.
- Centers wide crop for homepage so success is observable.
- The starter angle adds first successful run with safe defaults without extra fluff.
How to use it in Claude
When web teams review output, they should see first successful run with safe defaults without hunting for it. For product photography 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. 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.
Run a constrained version and a wild version of hero banner. Keep structure from one and energy from the other. 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 Starter 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-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 (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-starter: 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
- State the job (wide crop for homepage) in one line before any style talk.
- web teams should recognize themselves in the first paragraph.
- Document what changed when you customized slug hero-banner-starter.
- Claude improves when you paste a real snippet or reference still.
- Ship a draft, then tighten. Do not chase a perfect first token.
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 starter version stresses first successful run with safe defaults 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 starter angle for hero banner?
- Different angles solve different failures. Starter helps when web teams 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.