Claude for Designers: Generate, Edit, and Iterate Images in One Thread

1. Align on goal and constraints in Claude (audience, brand adjectives, must-nots).
2. Ask for 2 or 3 visual directions in prose first (cheap thinking).
3. Pick a direction; generate with AiWings (attach references if brand assets exist).
4. Critique with precision (“too corporate,” “type legibility,” “negative space”).
5. Edit the last generation. Do not re-roll the universe unless the concept is wrong.
6. Export winners to Figma / your layout tool for composition polish.

• Art director: turns vague client feedback into concrete visual constraints.
• Prompt librarian: rewrites messy notes into generation-ready language.
• QA partner: checks whether the still matches the brief after an edit.
• Documentation: keeps the decision trail next to the images for handoff.

• Pixel production under credit control.
• Reference-aware product or character continuity.
• Follow-up edits without re-uploading the last result by hand.

Name files and campaigns in chat (“Q3 serum hero v2”). Track which generation is client-approved. Keep rights on uploaded references clean. Disconnect project-specific connectors if you ever share machines, but usually OAuth is per user, not shared passwords.

Limit open branches. Prefer “edit last” over five parallel first prompts. When the brief flips completely, say so explicitly so Claude starts a new visual path instead of lightly restyling a dead concept.

Take one live client brief you would normally split across Claude and an image tab. Connect AiWings, run the loop above once, and note how many context switches disappeared.

Open AiWings and connect Claude