AI WORKFLOW · DESIGN CRITIQUELive workflow · UX case study
CritiqueAI · UX Critic Agent
Give the critique a task, not just a screen.
THE THINKING BEHIND THE INTERFACE
Give the critique a task, not just a screen.
A screen alone cannot explain who is using it or what they need to accomplish. CritiqueAI pairs screen uploads with optional task, platform, context, and website URL inputs. This case study examines the public workflow form and the UX reasoning behind that input structure; the internal agent graph and generated outputs have not been inspected.
DESIGNED FOR
Designers and product teams seeking a second perspective on an interface
A UX reading of the supplied artifacts. The sequence below explains the design logic, not a verified chronology of research. Intended benefits and proposed tests are not measured outcomes.
The user's path
Upload screen(s)
Describe the user task
Add platform and context
Execute the workflow
Review suggestions with human judgment
PROCESS & ARTIFACTS
How the problem becomes an interface.
01
Anchor the review in an artifact
The screen upload is the primary input. Local uploads and pasted file links give teams two ways to provide the same visual evidence.
02
Make context available without blocking entry
The public form labels user_task, platform, context, and Website URL as optional. These fields can give the critique a purpose beyond visual taste, while keeping the initial interaction lightweight.
03
Separate preparation from execution
An explicit Execute action gives the user a review point before sending their screens to an external workflow. Run Once and Run Batch are visible modes; batch behavior and output quality remain untested.
04
Close the loop with validation
A proposed next step is to compare feedback on the same screen with and without task context. Ask designers which observations are evidence-based, actionable, or incorrect.
Actual public CritiqueAI interface, captured before execution. No generated critique is shown.
WHY IT IS DESIGNED THIS WAY
Every choice has a reason. And a trade-off.
Context is optional, but valuable
A quick first run reduces setup friction; task context can help distinguish an actual usability problem from a stylistic preference.
THE TRADE-OFF
Without context, feedback may assume the wrong audience or task. Suggested follow-up: explain what each optional field improves.
Keep the designer accountable
An AI critique should inform a design decision rather than automatically approve or reject an interface.
THE TRADE-OFF
Human review adds effort, but unsupported or conflicting recommendations need to be challenged.
Treat uploaded screens as sensitive
Screens can contain customer data or unreleased work. Use redacted examples and review the hosting service’s policies before uploading.
THE TRADE-OFF
Redaction removes some context; a safe synthetic screen may be preferable for public demonstrations.
GOOD THINGS START WITH A CONVERSATIONKerala, India · Working everywhere