Mandatory multi-image generation without a clear budget cap may cause unexpected charges
Source references: 5The Skill requires image generation first, explicitly prefers too many images over too few, and permits second or third generations for the same section. An 8–12-section page could therefore trigger many billed generations and retries.
With a per-use or quota-based image service, the user could consume substantial paid credits, quota, and time before frontend implementation begins.
The source supports this risk. Visual website tasks mandate image generation first and prefer one image per section; complex or unclear sections may require extra images or regeneration. If the image service charges per request or usage, an 8–12-section site plus retries could create unexpected costs. No total-image, retry, or budget cap is stated. Users can ask for a pre-generation count/cost estimate, hard limits, and confirmation before exceeding them.
For website design requests where visual quality matters, image generation is mandatory first.This means:1. generate the design image or image set yourself first2. deeply inspect and analyze the generated image(s)3. extract the design system from them4. implement the frontend only after thatShow 4 other places
Strong rule:- it is better to generate too many clear images than too few compressed images- it is better to generate one clear image per section than one unreadable board for the whole site- it is better to create an extra detail image than to guess details laterNever reduce image count just for convenience if that harms quality.Default rule inside Codex:- 1 section requested → generate 1 image- 2 sections requested → generate 2 images- 3 sections requested → generate 3 images- 4 sections requested → generate 4 images- 5 sections requested → generate 5 images- 6 sections requested → generate 6 images- 7 sections requested → generate 7 images- 8 sections requested → generate 8 images- 9 sections requested → generate 9 images- 10 sections requested → generate 10 images- and so on when reasonableDo not hesitate to create a second or third extraction-oriented image for a section if the first image is too broad.If the user asks for:- a hero only → generate 1 hero image- 4 sections → generate 4 section images- 8 sections → generate 8 section images- 12 sections → generate 12 section images when reasonableGeneral preference:- one section = one primary image- one complex section = one primary image + one or more optional detail images- one unclear section = regenerate it again as a fresh clean standalone image