Workflows
IAD — Image A Day
One illustrated image per day, on theme.
Daily image generation via Nano Banana / Gemini Imagen — keyed off PAD topics or LAD lists. Builds a year of consistent on-brand visuals.
- Linked to PAD / LAD topics
- On-brand, consistent style
- Bulk export for social
Why
Daily content needs daily images. Tying generation to PAD / LAD topics removes the 'what should we make today' tax and gives a year of on-brand visuals for free.
How
- Pull today's topic from PAD or LAD
- Generate via Nano Banana / Gemini Imagen with brand style pack
- Auto-archive + bulk export for social
Proof
- Daily cadence
- 1 image / topic
- Provider routing
- Nano Banana · Gemini · DALL·E · Flux
- Style consistency
- brand pack v3
IAD — image a day, on brand
Topic in · Multi-provider out
Hover or tap a node to see details.
FAQ
- Why route across four providers instead of picking one?
- Each provider has a sweet spot — Nano Banana for editorial illustration, Imagen for photorealism, DALL·E for stylised, Flux for fast batch. The router picks the right tool per task, not per project.
- How do you keep four providers visually consistent?
- The style pack injects palette, mood, framing, and negative constraints into every prompt before it routes. Provider matters less than the constraints — same brand bones across rendering paths.
- Does every image get archived?
- Yes — every render is tagged with prompt, provider, style-pack version, and stored. Bulk export per channel is one CLI command; future re-renders never start from scratch.
In production
- xmas product hero batch
35 Runware-FLUX 1024×1024 product heroes rendered, S3-uploaded, Mongo-patched in one POM.
See it - PAD/LAD-keyed daily image
Daily image keys off whatever PAD or LAD chose. Zero 'what should we make today' tax.
- Brand style pack v3
Brand constraints (palette, mood, framing) enforced at prompt level across all providers.