Generative Visual Asset Architecture Handover

Role: Principal AI Creative Director and Design Systems Architect with 15+ years leading visual engineering in enterprise software.

Context

• Target software platform: {{software_platform}}
• Desired visual system and rendering aesthetic: {{target_visual_style}}
• Deployed image generation model and version: {{generative_model_engine}}
• Excluded artifacts and negative parameters: {{negative_prompt_parameters}}
• Production feature deployment scope: {{product_feature_scope}}
• Recipient leadership and technical team: {{stakeholder_audience}}

Task

Draft an authoritative, highly technical visual architecture email to {{stakeholder_audience}} establishing the modular prompt matrix, rendering parameters, and quality verification guardrails for generating production assets in {{software_platform}} across {{product_feature_scope}}.

Method

1. Translate the product context of {{software_platform}} into structured visual tokens optimized for {{generative_model_engine}}.
2. Deconstruct {{target_visual_style}} into programmatic components: lighting setup, camera focal length, material properties, depth of field, and compositional balance.
3. Construct 3 modular, production-ready master prompt formulas (Hero Canvas, Contextual Empty State, Micro-Feature Illustration) mapped to {{product_feature_scope}}.
4. Build an explicit negative prompt string incorporating {{negative_prompt_parameters}} to systematically eliminate hallucinations and geometry distortions.
5. Specify exact model parameters for {{generative_model_engine}} including aspect ratios, seed constraints, CFG scale/stylize values, and sampling steps.
6. Detail an automated or manual visual QA acceptance checklist to govern frontend staging approval.
7. Format the complete communication as a polished, professional engineering handover email.

Constraints

• MUST supply complete, copy-pasteable prompt recipes containing explicit token syntax.
• MUST NOT use ambiguous aesthetic terms without attaching technical rendering equivalents (e.g., map "clean look" to "diffuse ambient occlusion, octanRender, studio backdrop").
• MUST incorporate all exclusions listed in {{negative_prompt_parameters}}.
• Keep the executive rationale concise while preserving strict technical granularity for frontend engineers.

Output format

• Subject Line: Formatted as [ACTION] Generative Visual Architecture & Prompt Spec: {{product_feature_scope}}
• Section 1: Executive Rationale & Model Target (under 120 words)
• Section 2: Master Prompt Architecture Matrix (3 distinct asset prompts with token breakdowns)
• Section 3: Engine Parameter Configuration (bulleted syntax for {{generative_model_engine}})
• Section 4: Negative Prompt Specification & Defect Mitigation
• Section 5: QA Visual Acceptance Checklist (4 objective criteria)

Self-review

• Ensure every prompt formula directly enforces the aesthetic of {{target_visual_style}}.
• Verify all parameter flags are syntactically accurate for {{generative_model_engine}}.
• Confirm the email balances executive clarity for {{stakeholder_audience}} with developer-ready precision.