# Vintage B2B Wholesale YouTube Thumbnails Prompt
**Category:** Image Prompt → YouTube Thumbnails | **Audience:** Professionals or practitioners using AI for youtube thumbnails tasks. | **Delivery:** YouTube
**Job:** Produce a visually coherent asset that communicates the named concept and survives the intended use context.
## SOURCE INPUT
Use this source brief as the authoritative task/scenario. Preserve its supplied numbers, constraints, assets, frameworks and requested deliverables. Separate facts from assumptions; never invent missing evidence.
> Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims.
>
> > vintage youtube thumbnails concept 21 - b2b wholesale - premium commercial studio - unique angle 150, ultra-premium commercial YouTube Thumbnails for HR Tech ATS, hyperrealistic style, dramatic Rembrandt, 24mm wide lens, centered negative space composition, 8K ultra-detailed textures, professional color grading, Phase One IQ4 150MP Tech: --ar 21:9 --style raw --v 6.1 --q 2 --s 900 NEGATIVE: no watermark, no text typo, no low-res, no deformed, no oversaturated, no plastic skin, no AI artifacts VARIATIONS: wide master, close-up detail, copy-space 35% empty, dark mode, lifestyle in-context, flat lay knolling, seasonal, material triptych USE: YouTube Thumbnails hero for HR Tech ATS website/pitch/ad. Tested Midjourney v6.1 Flux Pro.
>
> ## CATEGORY-NATIVE PRODUCTION
> Intent → Visual Strategy → Category-Native Production → Model Adapter → Failure Prevention → Variant Test → Platform Adaptation → QA. Translate the brief into production-ready instructions. Lock the subject/identity first, then define the dominant visual idea, focal hierarchy, composition, viewpoint or shot design, environment/context, lighting, material or surface behavior, depth/scale, typography or copy-safe zones when relevant, aspect ratio and crop. Preserve all supplied reference invariants. For video, also define shot duration, action beats, camera movement, continuity anchors and transition logic. Do not add technical vocabulary that does not improve the specific asset.
>
> ## MODEL ADAPTER
> Adapt the production prompt to the requested model(s). Use precise semantic instructions for general models; use model-specific syntax only when supported. Never invent parameters or capabilities. If multiple models are listed, preserve the same creative intent while translating only the syntax/control layer.
## CREATIVE PRODUCTION SYSTEM
**Workflow:** Creative intent → subject/reference fidelity → composition → medium/category-native production → lighting/material or graphic logic → model adapter → failure prevention → variants → platform crop → QA
Translate the brief into observable production decisions:
- subject/reference invariants
- composition/hierarchy
- category-native medium/style logic
- lighting/material/graphic or motion behavior where relevant
- perspective/scale/continuity where relevant
- typography/text integrity when relevant
- aspect ratio/crop and final-use requirements
Do not add camera, cinematic, environmental or technical instructions that do not materially apply to this medium.
**Model adapter**
Target model(s): ChatGPT-4o, Claude 3.5, Gemini 1.5, Midjourney v6.1, Runway Gen-4, Sora. Keep creative intent model-neutral; adapt only supported syntax/capabilities. Never promise exact text, identity, geometry or motion behavior beyond what the model can reasonably deliver.
**Failure prevention**
Protect: subject/reference fidelity, composition supports intent, category-native visual logic, text/geometry constraints are realistic, final crop is usable. Also check identity/reference fidelity, accidental objects, contradictory perspective/scale, unusable crops and medium-inconsistent details.
**Output contract**
Return a production-ready prompt/plan with concrete visual decisions, constraints, negative/failure controls where useful, and a final-use QA checklist.
## FINAL GATE
Before answering, ask: Is this specific to the supplied scenario? Is every important instruction actionable? Are assumptions labeled? Is the output genuinely usable? Would a professional get a better result from this than from a generic prompt? If not, revise the weakest part before delivering.