assets/templates/image-generation-visual-asset-brief.md

# Image Generation Visual Asset Brief

Use this when an editorial visualization needs generated imagery, object marks, cutaways, textures, contextual backgrounds, or visual substrates.

## Story Role

- Visualization title:
- One-sentence takeaway:
- Asset role:
  - large-screen visual design concept
  - mobile portrait visual design concept
  - mobile landscape visual design concept
  - existing page integration concept
  - animation or scrollytelling key frame
  - data mark
  - contextual substrate
  - object cutaway
  - physical texture
  - scene background
  - thumbnail or social preview
- What the asset must help the reader understand:
- What the data layer will add separately:
- Evidence, caveat, source context, or annotation role the concept must preserve:
- Data, labels, axes, values, or source notes that must remain editable after implementation:

## Prompt Inputs

- Subject:
- Existing page, report, deck, app, or scene context:
- Viewpoint or camera angle:
- Composition:
- Target viewport or aspect ratio:
- Large-screen, mobile portrait, or mobile landscape variant:
- Style direction:
- Lighting:
- Background:
- Color constraints:
- Output format:
- Transparency needed:
- Aspect ratio:
- Batch count:
- Consistency requirements:

## Data Integration

- Which data fields bind to this asset:
- Label anchor points:
- Scale or perspective constraints:
- Regions that must remain clear for labels:
- Areas where data marks will overlay:
- Mobile crop behavior:
- Main visualization visibility behavior on mobile:
- Touch, pinch, keyboard, or settings-panel constraints:
- Spotty-connection, stale, or offline state to represent:
- AR, camera, motion, vibration, notification, or geolocation role, if any:
- Semantic design contract path:
- User design approval status, if this asset is a concept: pending / approved / rejected
- Approval response, date, or review note:
- Requested changes and iteration notes:
- Approved concept set path, if this asset is a concept:
- Paired large-screen concept path:
- Paired mobile portrait concept path:
- Paired mobile landscape concept path, if needed:

## User Review Response

- Concept image shown to user:
- Concise plan bullets:
- Concise interaction bullets:
- Approval question asked before project changes or implementation code:
- User response:
- Next iteration needed:

## Concept Contract Fidelity

- Locked asset or concept elements:
- Flexible production details:
- Label-safe regions that must be preserved:
- Data-overlay regions that must be preserved:
- Material deviations requiring user approval:
- Approved deviations:
- Concept-to-result traceability notes:

## Negative Prompt / Exclusions

- No publication branding or copied layouts.
- No text, numbers, axes, logos, or source notes inside the generated image unless explicitly required.
- No misleading scale cues.
- No decorative detail that competes with data labels.
- No invented factual objects when the story requires real-world specificity.
- No visual choices that weaken the claim, hide caveats, or imply unsupported precision.

## Review Checklist

- The generated asset supports scale, place, mechanism, motion, or stakes.
- It remains legible under the chart and annotation layer.
- It does not imply unsupported precision or causality.
- It can be described accurately in alt text.
- It has a static fallback and a mobile crop.
- If used as a concept, it was shown as part of the large-screen and mobile concept set with concise plan and interaction bullets, then approved or iterated before project changes or implementation code.
- If approved as a concept, it has been converted into a binding semantic design contract before implementation.
- The final asset or implementation matches the contract or records approved meaning-preserving deviations.