--- name: oneirloom-product-art-direction description: Inspect supplied product references and develop static ecommerce images, realistic product scenes, or creative advertisements. Resolve clear or vague briefs, preserve product facts through permitted transformations, and revise complete prompts across turns. --- # Product art direction Read the [shared interaction contract](../oneirloom/references/interaction-contract.md) before the first substantive response unless its unchanged content is already available. For person prompts, including new images and grid panels, read [person defaults and proportions](../oneirloom/references/person-prompts.md). Use this method for static ecommerce visuals based on a real product, including catalog images, breakfast scenes, sale graphics, miniature worlds, and revisions. It supplies product decisions within the existing graphic-design process. It does not build stores, accounts, membership systems, or videos. ## Workflow When the current task creates or redesigns a composed graphic, read [graphic design](../oneirloom-style-design/SKILL.md). It owns process order, composition, production selection, and review. A local revision can reuse the confirmed design without a fresh creation read. The steps below supply its product understanding and concept decisions. Isolated product photography and story scenes use the relevant medium method without forcing graphic layout. 1. Inspect the current product before selecting a concept or template. View the supplied image directly, or use `view_image` for a local file. Reuse observations from an unchanged image; inspect replacement images and changed crops. Record source-supported silhouette, proportions, packaging, visible materials and colors, quantity, marks, readable text, and supplied specifications. Keep product identity separate from staging. Leave illegible text, hidden fillings, internal construction, ingredients, effects, and experience claims unknown. User-stated facts retain their provenance; recording them does not certify them. With only a text fixture, identify it as supplied text rather than inspected imagery. 2. Use the brief that exists. If the intended use, direction, and necessary facts are clear, give a short reasoned design and complete prompts directly. For a vague selling request, inspect the available material first, then ask only the few missing questions that change the design. Offer two or three materially different, reasoned directions when that helps the user choose. Develop the chosen direction into a complete prompt. Do not require a questionnaire, a realism/creativity mode selection, or approval of every internal decision. Read [ecommerce collaboration](references/ecommerce-workflow.md) only for a vague brief, useful external research, unresolved copy handling, or a portable assistant handoff. A clear prompt request does not require it. 3. Connect the concept to this product and the current intent. Use an observed shape, surface, repeated part, material, or use relationship to explain why the scene fits. Carry forward explicit styles and spatial choices. A clear brief need not be reopened as a menu. For exploration, alternatives may use different mechanisms; after selection, keep one coherent main idea and a clear product hierarchy. Decide what stays literal and what the agreed creative treatment transforms. Keep perspective, ground plane, contact points, and light coherent unless an intentional transition has a visible reason. 4. Preserve product truth through the chosen treatment. Realistic scenes retain supported product geometry, package identity, color, quantity, readable text, and specifications. Do not add an unseen filling, implied ingredient, internal construction, effect, dimension, origin, or experience. Unsupported steam, bursting fillings, performance demonstrations, sensory promises, and health promises can imply product facts. Similar products and style references do not establish this item's facts. A proposed use scene is a creative choice, not evidence of actual use or performance. Creative scenes may use scale changes, miniature factories, ingredient architecture, fantasy, or anthropomorphism when they serve the agreed intent. Explain which objects are imaginary scenery and write that relationship visibly into the prompt. Confirmed chocolate may become a chocolate building; unknown bread filling cannot become a strawberry-production claim. Use crust or shape as the miniature mechanism, or a clearly separate themed world, when ingredient facts are missing. Do not impose documentary realism on an agreed fantasy. A station around an intact crust differs from a production line pumping unverified strawberry filling into the bread; judge both the artistic intent and the factual implication. 5. Resolve factual conflicts before the dependent depiction. If a supplied image and a user statement disagree about a critical product property, surface the conflict and ask for the intended source or correction. Continue independent layout and style work. An explicit creative transformation changes its agreed visual dimension; it does not silently establish a new fact about the item sold. A confirmed factual correction updates the notes with its source. Preserve other valid product constraints. An imagined blue wrapper is a campaign transformation; a statement that the current pack is blue and the photo shows an older edition is a user-stated factual correction. Keep that provenance. If the intended meaning is unclear, ask before depicting either as the sold item. 6. Integrate the product, concept, copy, and composition into a complete prompt. State concrete shape, position, material, scale, and relationships instead of relying on “keep it real” or a stack of prohibitions. Assign each reference its responsibility outside the prompt block. Keep internal unknowns and acceptance checks outside generation prose. Apply the shared contract's final-assembly and fenced-block rules. If exact brand or package text is requested but unreadable, request readable evidence and continue independent layout. Do not silently substitute an unreadable-label delivery. Offer an explicitly described angle or crop alternative for the user to choose. Original-label compositing requires a readable source and an available suitable tool. An agreed alternative may leave unresolved lettering unreadable, but generation cannot be promised to recover missing text. Only after the current concept is resolved, consult a relevant historical case if useful. The [chocolate poster](../oneirloom-style-design/templates/product-origin-world/template.md) records one accepted product pairing, not a reusable river or origin-world recipe. The [takeaway food town](references/takeaway-food-town/case.md) records a source-specific relationship: spring rolls become shop roofs, fries form steps, and the opened box carries a continuous hand-drawn street. An earlier rejected transfer kept the meal unchanged above a separate street and joined them with an oversized sauce waterfall. These records support product-specific integration, not a town requirement or repeatability claim. ## Revision and delivery Apply the shared contract's continuity rules in the active conversation. A background edit preserves product facts and valid design choices. Changed copy may require explained layout reflow. Replace a rejected direction while retaining valid facts, and return the complete revision. Keep reusable product and style descriptions for later static frames without starting Live or video work. For an optional handoff example, the [Chinese worked exchanges](references/ecommerce-examples.md) demonstrate explicitly Chinese-only requests with supplied text fixtures. They are historical teaching material, not generated or visually verified results. When a result is available, compare original product evidence, current agreed intent, the submitted prompt if available, and the result. Check product and package structure, supported text and quantity, prominence, material continuity, concept readability, and food appeal. Judge intentional transformations against the agreed design. Hand misses to `oneirloom-result-diagnosis`; a failed result never becomes the new product specification. State whether the result was inspected, user-reported, or unavailable. A prompt-only delivery remains ungenerated and visually unverified.