Claude prompt for product photography: Hero Banner (Workflow)
Claude · Product Photography · Workflow
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: operational. Optimize for step order, checkpoints, and handoffs.
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 strong Claude product photography hero banner prompt names the job, audience, and finish line. This page does that for web teams. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
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
- Separates draft from critique so you can steal the structure later.
- Names a clear job so Claude does not wander into generic advice.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Repeats the hard constraint: negative space for type.
- Keeps product photography vocabulary specific instead of buzzwords.
How to use it in Claude
Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models. Save the winning variant for hero banner — teams with a short library ship faster. Ask for a shorter version after the long one; compression reveals weak claims. Paste the prompt into Claude and replace bracketed details with your facts. If the first answer is vague, reply with the constraint again: negative space for type.
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 Workflow 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-workflow when step order, checkpoints, and handoffs 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
Anthropic users working on hero banner in product photography should treat "negative space for type" as non-negotiable. Pack shots, lifestyle scenes, and catalog consistency. When web teams run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste negative space for type as the first follow-up message — do not rewrite the whole prompt.
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.
- Document what changed when you customized slug hero-banner-workflow.
- State the job (wide crop for homepage) in one line before any style talk.
- The Workflow variant is for step order, checkpoints, and handoffs.
- Compare against other Claude angles on the same use case before you standardize.
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 workflow version stresses step order, checkpoints, and handoffs 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 workflow angle for hero banner?
- Different angles solve different failures. Workflow helps when web teams need step order, checkpoints, and handoffs. 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.