nano banana face swap prompt: editing prompt

Define the transformation prompt brief behind nano banana face swap prompt

For Nano Banana Face Swap 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. Name the source attributes that must remain unchanged, the single intended edit, protected identity or product details, and a reversible review path. Editing, swapping, or upscaling language is a proposed transformation and does not establish that a tool can perform it. 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. At the next gate, preserve the evidence table, and ask the delivery owner to record evidence freshness before the production checkpoint.

Apply 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 face swap 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. At the next gate, preserve the review copy, and ask the delivery owner to record source fidelity before the production checkpoint.

• Portable shot contract Before approval, preserve the delivery checklist, and ask the claims reviewer to record visible continuity before the editorial approval.
• Dated model-control notes Before approval, preserve the reference set, and ask the channel editor to record revision intent before the editorial approval.
• Version and access verification Before approval, preserve the claim inventory, and ask the policy reviewer to record source fidelity before the editorial approval.

Prepare 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. Before approval, preserve the rights memo, and ask the channel editor to record control availability before the bounded test.

Build controlled variants and observable acceptance checks

For this owner, the first review pass should make nano, banana, face, swap observable rather than merely decorative. Change one meaningful dimension per version and label the hypothesis, invariant details, expected difference, and rejection condition. Approve only when the requested change is authorized, boundaries are explicit, identity and factual attributes remain faithful, and artifacts can be compared with an untouched source. Keep failed variants in the decision record so the final wording is explainable rather than selected by impression alone. During review, preserve the rights memo, and ask the model evaluator to record format readiness before the dated decision.

Review 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. For this checkpoint, preserve the rights memo, and ask the identity reviewer to record control availability before the fallback decision.

Approve 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 face swap 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. For this checkpoint, preserve the reference set, and ask the identity reviewer to record revision intent before the scope confirmation.