frontend-imagegen-directorlisted

# Frontend Imagegen Director This skill is not a prompt-only mockup generator. Its default workflow is: 1. inspect the current project's style and product nature 2. clarify the user's page requirements in a Superpowers-style flow 3. confirm the extracted requirements before image generation 4. generate a front-end concept image with `gpt-image2` or the environment's image generation path 5. use that image as the visual contract for the actual front-end implementation If the user explicitly asks for image-only output, you may stop after the image stage. Otherwise, do not stop at the image. ## Required Outcome Before finishing, state which of these outcomes you are delivering: - image plus implemented page - image-only exploration - prompt-only fallback If the user asked to "draw the front end and then build it", the required outcome is `image plus implemented page`. ## Dependency Rules - Requirement clarification should use `superpowers` when it is actually available. - If `superpowers` is not available, do the same requirement-discovery discipline manually and explicitly say it is a fallback. - Prefer `gpt-image2` or `gpt-image-2` when the environment allows model-path selection. - If the environment only exposes built-in `imagegen`, use that path and describe it accurately instead of pretending direct model control exists. - If no image generation capability exists, do not pretend you generated anything. - In that fallback case, stop at a requirement summary, proje