01Define the model-specific prompt plan behind nano banana headshot prompt
For Nano Banana Headshot Prompt, state the subject, environment, action objective, emotional beat, and end condition in plain production language. These invariants keep model-specific prompts variants comparable instead of producing unrelated ideas. Resolve the exact named model or version, then keep creative direction separate from claims about access, syntax, limits, price, audio, duration, quality, or availability. Use only dated first-party evidence for those changing facts. Write the decision owner and intended handoff beside the brief so a search phrase cannot be mistaken for a verified product capability or an instruction that has already been executed. For this decision, preserve the failure note, and ask the workflow owner to record evidence freshness before the dated decision.
02Apply the model-specific prompts structure
Write a portable core prompt before adding any vendor or version vocabulary. Keep the subject, action, spatial relationship, shot order, continuity anchors, and end condition independent from a named model. Put model-specific controls in a separate dated note so an unsupported parameter cannot quietly become part of the creative brief. For “nano banana headshot prompt”, keep a visible distinction between required content, optional treatment, exclusions, and facts that need evidence. That structure gives controlled variants a stable baseline and lets a reviewer identify which instruction caused a material change. For this decision, preserve the brief version, and ask the brand reviewer to record format readiness before the reversible handoff.
03Prepare authorized inputs for identity and portrait treatment
This query calls for authorized likeness references, the intended presentation, protected facial and body attributes, and documented consent for the use context. Describe pose, expression, framing, light, wardrobe, and background without fabricating identity, endorsement, personal history, or intimate context. Keep face or person changes explicit and reversible. Record the source, permission, intended audience, protected details, and reviewer before testing language. The goal is a traceable creative proposal, not an assumption that a named platform, model, or workspace will perform the requested action. For the named reviewer, preserve the continuity note, and ask the claims reviewer to record input provenance before the editorial approval.
04Build controlled variants and observable acceptance checks
For this owner, the first review pass should make nano, banana, headshot observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. The brief is reviewable when its creative core remains portable and every model-dependent statement is either cited with a date or clearly labeled as an open test question. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. At this stage, preserve the continuity note, and ask the creative lead to record disclosure clarity before the controlled revision.
05Review authorization, safety, and changing product facts
Reject deceptive impersonation, sexualized manipulation, non-consensual face or body swaps, and any use involving minors or a person whose authority is uncertain. Any identifiable face, body, voice, selfie, portrait, or personal image requires explicit permission, a legitimate purpose, dignity safeguards, disclosure where required, and review against impersonation or deceptive endorsement. The named third-party model or product requires dated first-party verification for identity, version, access, inputs, controls, limits, pricing, licensing, and output behavior; this page makes no comparison or SEELE availability claim. Treat every named model, competitor, access term, platform rule, identity use, commercial claim, and output specification as a dated evidence question. If authorization or first-party support is missing, keep the language editorial, stop the handoff, and record the unresolved gap instead of inventing a workaround. In the decision log, preserve the brief version, and ask the production lead to record disclosure clarity before the release review.
06Approve a reversible prompt handoff
Confirm the exact provider, version, access surface, accepted inputs, controls, and output behavior against current first-party material before a test. A model name in a query is an evaluation target, not proof that SEELE or any other product currently exposes it. Before approving “nano banana headshot prompt”, check purpose, source rights, identity consent, factual support, continuity, disclosure, destination requirements, and the named review owner. Preserve the original brief and version notes. This handoff supplies authored guidance only and neither runs generation nor guarantees access, quality, speed, licensing, publishing, downloads, or outcomes. In the decision log, preserve the input snapshot, and ask the continuity editor to record source fidelity before the source comparison.
