Image Prompt

Hyperrealistic Femtech - Premium Co Sci-Fi Prompt — Performance / Conversion

PROMPT

# Hyperrealistic Femtech - Premium Co Sci-Fi Prompt — Variant 1

## EXPERT ROLE
Act as a senior Sci-Fi specialist. Solve the exact task. Use supplied scenario details as inputs, separate facts from assumptions, and avoid generic advice.

## INTENT
**Job:** Produce a visually coherent asset that communicates the named concept and survives the intended use context.
**Audience:** Professionals or practitioners using AI for sci-fi tasks.
**Context:** Primary professional application
**Success:** define 2–4 observable criteria tied to the requested outcome.

## WORKING BRIEF
Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims.

> hyperrealistic sci-fi concept 38 - femtech - premium commercial studio - unique angle 269, ultra-premium commercial Sci-Fi for Legal Tech, cinematic style, studio softbox, 85mm f/1.4 lens, centered negative space composition, 8K ultra-detailed textures, professional color grading, Phase One IQ4 150MP Tech: --ar 16:9 --style raw --v 6.1 --q 2 --s 750 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: Sci-Fi hero for Legal Tech 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.

## FAILURE PREVENTION
Address only relevant risks: identity drift or subject distortion; incoherent composition or focal hierarchy; incorrect material/lighting behavior; text or logo corruption when present; platform crop failure. For each selected risk, state the prevention rule and the visible QA signal that proves it is controlled. Treat supplied logos, text, faces, products, proportions and other identity-critical references as invariants.

## VARIANT + PLATFORM TEST
Create up to three controlled variants only when useful: A changes composition, B changes one treatment variable, C changes context/crop/platform presentation. Preserve identity and strategic intent. For each variant state the hypothesis, variable, success signal and decision. Adapt crop, safe areas, viewing distance, text density and hierarchy to the actual platform without changing the core concept.

## PROFESSIONAL HANDOFF
Return the final generation-ready prompt plus the key inputs, locked invariants, negative/failure-prevention rules, target aspect ratio, platform adaptation and QA checklist. Make the result usable by a designer, art director, marketer or production team without needing to reconstruct missing decisions.

## QA
Check intent, category-native quality, identity/reference integrity, composition, technical coherence, temporal continuity for video, platform fit, text/logo fidelity where relevant, failure prevention and professional usability. If a critical gate fails, make the smallest responsible correction and rerun the relevant check.

## OUTPUT CONTRACT
Return a specific, immediately usable result. Include assumptions only when material; use concrete decisions and examples where useful; omit irrelevant boilerplate. Do not merely restate this prompt.

## V8.5 STRATEGIC DIFFERENTIATION

**Strategic job:** Performance / Conversion
**Decision/use-case:** conversion or performance use case
**Category-native workflow:** world premise → technology logic → environment → scale → material language → narrative focal point

### Intent Lock
Solve one problem: Optimize the asset for a measurable user action, with the focal hierarchy and output designed around conversion.
Do not let generic style language substitute for the strategic job.

### Differentiation Rule
This record is intentionally different from sibling variants by changing the **strategic objective and decision context**, not merely adjectives, palette, or wording.

### Production Emphasis
Make the primary user action, benefit, or decision unmistakable; remove decorative elements that compete with it.

### Controlled Experiment
Test this strategic lens against the strongest alternative while keeping the supplied subject/brand facts stable. Compare the outputs on:
1. task comprehension,
2. category quality,
3. audience fit,
4. professional usefulness,
5. platform/use-case performance.

### Decision Rule
Keep this version when its strategic lens produces a materially better result for the stated use case. If it does not, revise the lens-specific execution rather than adding decorative variation.

## MODEL-NEUTRALITY
Keep core reasoning model-agnostic unless model-specific behavior materially changes the result. When a model is specified, adapt only the relevant syntax or capability.

## DELIVERY FIT
Optimize the final artifact for **Primary professional application** only where platform behavior changes the format, attention pattern, constraints, or delivery.

## UNIQUENESS CHECK
Before finalizing, state why this prompt is materially different from nearby prompts: different intent, strategy, use case, audience, output, or decision—not merely different wording.