Pack the right inputs

For develop an original campaign key visual from a rights-cleared creative brief, assemble only what changes the answer: communication goal, audience, mood board rights, composition, medium, palette, copy space, brand constraints, and rejection criteria. Label each item by authority and date. A source-of-truth document outranks a memory-based note; a current error log outranks a description of last month's behavior. State conflicts instead of letting the model blend them.

Use a four-part packet: task, evidence, constraints, and output contract. Put untrusted content inside clear delimiters and say that it is data, not instruction. Include representative examples, especially one normal case and one boundary case. Omit irrelevant history; excess context can hide the one line that controls the result.

Create three concept directions for a neighborhood night-market poster. Goal: communicate handmade food and evening community. Medium: bold paper-cut collage; palette: indigo, coral, cream; leave top third clear for approved copy. No logos, readable generated text, named living-artist imitation, copyrighted characters, or identifiable people.

Before sending, annotate the packet. Mark which values are verified, which are illustrative, and which are unknown. If a screenshot is involved, transcribe critical small text. If structured data is involved, include headers, units, software version, and null behavior. If creative material is involved, record ownership and permitted use. This is how context becomes operational rather than decorative.

A useful response would look like this: Three distinct, art-directable concepts described by composition, focal point, palette, texture, and intended audience response. That description is intentionally observable. “Looks good” is not acceptance. The operator must compare against the brief, inspect hands/faces/text, check brand fit and accessibility, run a reverse-image similarity check when appropriate, and confirm asset licenses. Keep the source material beside the draft so review means comparison, not memory.

The privacy boundary is specific: use only owned or licensed references; secure model releases for identifiable people; do not upload confidential client boards or unreleased brand assets. Create the smallest synthetic example that preserves the problem. Replace names and identifiers consistently so relationships remain testable. Redaction is not merely drawing a box: crop surrounding notifications, remove metadata where relevant, and check that hidden sheets, comments, or revision history are not included.

Poor packets lead to predictable failures: style-name imitation; generic mood words; accidental trademarks; generated gibberish text; endless variation without selection criteria; hidden reference rights. Another common failure is silently changing the source packet mid-run. Save a version or hash of the inputs beside the output, especially when another person will reproduce the work.

Rate a packet from zero to two on six dimensions: relevance, authority, recency, completeness, privacy, and reproducibility. A score below two on authority or privacy blocks the run. A low completeness score does not invite invention; it creates a question for the owner.