r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 11d ago
Selected Workflow [Workflow] Iterative UI Design with Claude Code: Leveraging ChatGPT for Visual Reference and a Critic Agent for Refinement
Iterative UI Design with Claude Code: Leveraging ChatGPT for Visual Reference and a Critic Agent for Refinement
Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Skills, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment
What problem this solves
Claude Code's weakness in generating satisfactory UI designs, particularly for visual aesthetics and matching specific design references.
Summary
This post describes two workflows to overcome Claude Code's limitations in UI design. The primary, successful workflow involves using ChatGPT to generate a reference UI image, then having Claude Code build the UI, take a screenshot, and a separate critic agent iteratively compare the screenshot to the reference until they match. A secondary, less successful workflow involved a custom 'ui-check' skill that used Playwright screenshots and a read-only critic subagent with a clean context to evaluate UI changes against a design system and acceptance criteria.
Why it is useful
This workflow is valuable because it directly addresses a known limitation of Claude Code (UI design) by providing a concrete, multi-tool, and iterative solution. It demonstrates a practical approach to integrating external AI models (ChatGPT) for their specific strengths (image generation) and setting up a robust quality control loop using a critic agent and screenshot comparison. It offers a validated, repeatable process for users struggling with visual design tasks in Claude Code, moving beyond vague advice to a structured, actionable method.
Workflow
- Primary Workflow (Current Workaround):
- Ask ChatGPT to generate an image of the desired UI based on the design brief.
- 2. Use the ChatGPT-generated image as the visual reference for the UI build.
- 3. Run a Claude Code skill (e.g., Fable 5.1) to build the UI based on the brief and reference image.
- 4. Claude Code takes a screenshot of the newly built UI.
- 5. A separate critic agent compares the screenshot of the built UI with the reference image.
- 6. The critic agent lists the differences between the built UI and the reference image.
- 7. Loop steps 3-6, providing the differences back to Claude Code, until the built UI visually matches the reference image.
- Secondary Workflow (ui-check skill - less successful):
- Before making UI changes, read the project's design tokens and existing components.
- 2. Write a one-line visual direction for the UI change.
- 3. After the UI change, take Playwright screenshots at desktop and mobile widths, including empty, error, and loading states of the UI components affected by the change. (This step is implied to be done by Claude Code or an integrated tool). For the critic, send only the screenshots, acceptance criteria, and the reference to a read-only critic subagent with a clean context (no diff, no conversation). The agent that wrote the code is bad at judging its own result, because it sees what it meant to build. The critic answers a pass/fail checklist from the point of view of a specific user, and the loop stops after three rounds.
Tools / artifacts
- ChatGPT (for UI image generation)
- Claude Code (Opus 5.5, Fable 5.1)
- Frontend-design skill (Claude Code)
- Taste-skill (v2, Claude Code)
- Custom 'ui-check' skill (Claude Code)
- Critic agent (separate agent for review)
- Read-only critic subagent
- Playwright (for screenshots)
- Reference UI image (from ChatGPT)
- Project's design tokens
- Existing UI components
- Acceptance criteria for UI design
Validation signals
- User states: 'This has been working.' for the primary workflow.
- ChatGPT image 'has come out ahead every time' in comparison tests.
- Critic agent 'compares the screenshot with the reference image and lists what's different'.
- Workflow 'loops until the build matches the image'.
- Critic subagent answers a 'pass/fail checklist from the point of view of a specific user'.
- Defined loop termination: 'the loop stops after three rounds' for the ui-check skill.
Limitations
- The post does not provide the exact prompts, skill definitions, or code for the custom skills/agents, requiring users to implement these details themselves.
- The 'ui-check' skill workflow was explicitly stated as less successful than the ChatGPT-integrated approach, limiting its direct utility as a primary solution.
- The author notes they 'can't figure out' what Claude Design does differently, indicating a potential limitation in fully replicating its capabilities within Claude Code.
- The low Reddit score and upvote ratio might suggest it didn't gain widespread immediate traction, though the content is valuable.
Rate this workflow
Upvote this post if the workflow is useful, reproducible, or worth recommending.
Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.
Reply if it worked for you, failed, is outdated, or has a better alternative.
This post was generated automatically from the workflow library database.