# Z-Image Turbo deck asset QA notes

Use this when generating pitch-deck imagery with local Z-Image Turbo through ComfyUI.

## What worked

- Z-Image Turbo produced much more premium portrait/editorial assets than SD1.5 for deck visuals.
- A single test image should be generated and visually reviewed before launching a full batch.
- For deck imagery, prompts should explicitly say `no text, no typography, no logo, no readable numbers` because Z-Image can still create convincing fake UI words.
- Contact sheets are the fastest QA format: generate thumbnails of all candidates, label with asset names, then classify each as KEEP / REGENERATE / USE ONLY BLURRED.

## Common reject reasons

- Fake UI titles or labels, e.g. generated dashboard/tablet text.
- Calendar or planning visuals containing pseudo-words or fake weekdays.
- Closing images where the crop creates a headless/body-only mannequin feeling.
- Dashboard images with readable-looking UI noise.

## Practical recovery pattern

1. Keep strong editorial/person images if anatomy, crop, and mood are good.
2. Regenerate tablet/timeline/dashboard assets with stronger negative prompts:
   - `text, words, letters, typography, readable text, logo, watermark, UI text, numbers, labels`
3. For business UI imagery that is otherwise attractive but has fake details, use a heavy blur/crop as abstract mood only.
4. Replace any weird closing silhouette with a known-good hero portrait instead of forcing a weak new image.
5. Rebuild a full deck contact sheet after integration, using the same HTTP path users will open, so relative image paths are actually loaded.

## Verification checklist

- [ ] Every final image has been opened or included in a contact sheet.
- [ ] No obvious fake text/glyphs remain, except safely blurred abstract UI.
- [ ] No bad hands/faces/anatomy are visible.
- [ ] No explicit or off-brand content.
- [ ] Mobile and desktop screenshots render with the final images loaded.
- [ ] The public URL serves the deck and image asset paths resolve.