01Define the model-specific prompt plan behind nano banana logo prompt
For Nano Banana Logo 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 checkpoint, preserve the control log, and ask the continuity editor to record reversal cost before the fallback 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 logo 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 checkpoint, preserve the claim inventory, and ask the workflow owner to record temporal order before the scope confirmation.
03Prepare authorized inputs for brand and product fidelity
This query calls for approved product facts, authorized brand assets, the exact variant, observable attributes, and the intended commercial or design context. Preserve color, scale, packaging, included items, marks, and supportable behavior. Separate a creative proposal from a factual depiction and flag stylization that could misrepresent the item. 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 a controlled test, preserve the failure note, and ask the identity reviewer to record failure conditions before the dated decision.
04Build controlled variants and observable acceptance checks
For this owner, the first review pass should make nano, banana, logo 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. Before delivery, preserve the input snapshot, and ask the identity reviewer to record source fidelity before the evidence refresh.
05Review authorization, safety, and changing product facts
Do not imply trademark clearance, commercial rights, product performance, campaign approval, or a fabricated customer experience from a prompt example. Advertising, UGC, product, and brand language requires substantiated claims, authorized assets and identities, transparent synthetic-media treatment, current destination-platform policy review, and no fabricated testimonial or performance outcome. 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. Before revision, preserve the review copy, and ask the creative lead to record format readiness before the controlled revision.
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 logo 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. Before revision, preserve the handoff draft, and ask the claims reviewer to record claim scope before the delivery pass.