Claude prompt for product photography: Scale Reference (Common Fixes)
Claude · Product Photography · Common Fixes
You are a exacting editor using Claude for product photography, specifically scale reference.
Job: communicate size.
Audience: hardware. Constraint: one familiar object.
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.Claude users in product photography use this scale reference prompt to ship faster drafts that respect "one familiar object". Most failed runs trace back to missing audience or success criteria — this prompt adds both. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Picture a hardware professional opening Claude with one job: scale reference. Without "one familiar object", answers drift. This page prevents that drift. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Keeps product photography vocabulary specific instead of buzzwords.
- Forces an output contract: headings, examples, and a final version.
- Repeats the hard constraint: one familiar object.
- Names a clear job so Claude does not wander into generic advice.
- Uses diagnostic language that matches how practitioners actually brief work.
How to use it in Claude
For product photography work, paste claude handles long briefs, policy-aware writing, and stepwise reasoning as a one-line reminder above the prompt. Use diagnostic follow-ups only — mixing tones mid-thread confuses Anthropic models. Redact client names; keep structure. Slug scale-reference-fixes is your canonical URL for this brief. This Common Fixes path is for hardware who care about communicate size. Ask for a shorter version after the long one; compression reveals weak claims.
Swap the audience once. If the scale reference piece still works, the core is solid. For scale reference in product photography, the failure mode is usually too many jobs in one ask. This prompt blocks that by design — especially "one familiar object". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for scale reference; they cannot invent metrics or brand rules. brand and ecommerce teams teams bookmark slug scale-reference-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 (hardware, offer, timeline).
- Confirm the constraint is still visible: one familiar object.
- 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 Scale Reference, 3 short sections, bullet list of recommendations, closing line that states one familiar object. Facts you supply appear; nothing invented.
Common mistakes
- Using the Common Fixes prompt but editing it into a vague one-liner.
- Deleting "one familiar object" to save space — that is usually the whole point.
- Pasting confidential data instead of redacted placeholders.
Expert notes
This Claude page targets "communicate size" for hardware. Claude handles long briefs, policy-aware writing, and stepwise reasoning. The diagnostic tone keeps typical failures and how to repair the prompt visible while you edit.
Workflow tip: save three winning outputs for scale reference and diff them. The shared skeleton becomes your team standard inside Claude.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a scale reference 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
- Keep one familiar object visible in the prompt, not only in your head.
- State the job (communicate size) in one line before any style talk.
- 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.
FAQ
- What is a Claude prompt for scale reference?
- It is a structured brief that tells Claude how to produce product photography output for hardware. This common fixes version stresses typical failures and how to repair the prompt and keeps "one familiar object" 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 "one familiar object" should stay unless your brief truly changed.
- Why use the common fixes angle for scale reference?
- Different angles solve different failures. Common Fixes helps when hardware 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.