Claude prompt for product photography: Hero Banner (Advanced)
Claude · Product Photography · Advanced
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: 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 Claude prompt for product photography is a copy-ready brief for hero banner aimed at web teams. 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, 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
- Names a clear job so Claude does not wander into generic advice.
- Forces an output contract: headings, examples, and a final version.
- Locks the audience (web teams) before style so tone stays honest.
- Centers wide crop for homepage so success is observable.
- Repeats the hard constraint: negative space for type.
How to use it in Claude
If the first answer is vague, reply with the constraint again: negative space for type. This Advanced path is for web teams who care about wide crop for homepage. Redact client names; keep structure. Slug hero-banner-advanced is your canonical URL for this brief. Ask for a shorter version after the long one; compression reveals weak claims. Save the winning variant for hero banner — teams with a short library ship faster.
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 Advanced 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-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 (web teams, offer, timeline).
- Confirm the constraint is still visible: negative space for type.
- For product photography 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 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
Practitioners choose Advanced when hero banner needs constraints, evaluation, and edge cases. Claude from Anthropic still needs your facts — especially for negative space for type.
For product photography, compare this Advanced prompt against the Quick Start and Expert angles on the same use case. Keep the structure that scores higher on wide crop for homepage.
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
- Product Photography work needs pack shots, lifestyle scenes, and catalog consistency.
- Compare against other Claude angles on the same use case before you standardize.
- web teams should recognize themselves in the first paragraph.
- The Advanced variant is for constraints, evaluation, and edge cases.
- 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 advanced version stresses constraints, evaluation, and edge cases 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 advanced angle for hero banner?
- Different angles solve different failures. Advanced helps when web teams 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.