Image Generation Provider Boundaries

Public wiki illustrations can make Rocky feel premium, but provider boundaries and image QA are part of the publishing process.

Respect provider intent

• Use the configured/approved image provider for production illustrations.
• If the requested Banana or Nano Banana provider is unavailable, do not silently substitute another provider.
• Create prompt specs and continue with text work until Kevin approves a different provider.

Prompt spec checklist

• Page slug and intended placement.
• Art direction, mood, color palette, and composition.
• Explicit instruction to avoid readable secrets, customer data, or real usernames.
• Text-free or near-text-free image requirement; readable labels should be HTML/CSS instead.
• QA notes for cropping, duplicates, and mobile fit.

Pitfalls

• Generated images can hallucinate logos, passwords, or fake UI labels.
• Exact text inside generated images is unreliable; composite text separately.
• A hero image reused too often makes the wiki feel cloned.

Verification steps

• Inspect the generated image before wiring it to a public page.
• Confirm file size, dimensions, alt text, and route rendering.
• Check desktop and mobile crops.
• Verify no private names, paths, API-key-shaped strings, or customer details appear in the pixels.