01
Run critique loops where the agent applies named dimensions and the human makes the calls.
Course / Intermediate
Design Review and Critique with Agents
Critique is where design quality is actually decided, and it is the part of the process most teams under-resource. This course covers using agents to make review sharper and more frequent without outsourcing taste: structured critique loops, heuristic evaluations and cognitive walkthroughs run at a scale no team could staff, visual regression evidence, accessibility and content review, and design review wired into every pull request.
- Modules
- 5 modules
- Total time
- ≈3h 50m
- Last updated
- 2026-06-02
- Your progress
- 0/5 modules completed
Audience and outcomes / 01
By the end of this course you can…
Design leads, senior designers, and design-minded engineers responsible for review quality — particularly teams where critique currently depends on whoever has spare time that week.
02
Execute heuristic evaluations and cognitive walkthroughs across whole products with evidence per finding.
03
Use screenshot-based regression evidence so visual review stops relying on memory.
04
Run accessibility and UX-writing reviews as standard passes rather than special projects.
05
Wire design review into every pull request with clear severity levels and human escalation.
06
Keep taste and final judgement human while making the mechanical parts of review continuous.
Curriculum / 02
Modules
Every module has a full slide deck with speaker notes and a narration script.
01
Critique Loops with Agents
The structure of a useful critique loop: named dimensions instead of vibes, the agent as a tireless first reviewer, and the difference between feedback an agent can act on and feedback that needs a human decision.
02
Heuristic Evaluation and Cognitive Walkthroughs at Scale
Two classic methods most teams skip because of cost, run across an entire product by agents: standard heuristics applied screen by screen, task-based walkthroughs step by step, and the human pass that turns findings into decisions.
03
Visual QA and Regression Evidence
Replacing it looked fine last time I checked with evidence: screenshot baselines, agent-run sweeps across states and breakpoints, and regression reports a designer can act on in minutes rather than re-checking everything by hand.
04
Accessibility and Content Review
Two reviews that are chronically deferred, made routine: accessibility sweeps that go beyond automated contrast checks, and UX-writing review that holds copy to the product's voice with the same rigour as the visuals.
05
Design Review on Every PR
The end state: every change that touches the interface gets a design review automatically — token and component checks, screenshot evidence, severity levels — with humans reviewing what matters instead of everything or nothing.
Related material / 03
The sources behind this course.
The course teaches the practice; the books and articles carry the depth, sources, and worked runs it draws on.
The Agentic Designer
The operating model for product designers, design leads, and builders who need to understand what changes when agents join design work.
Visual QA With Agents
A long-form workflow for using agents to inspect screenshots, compare implementation against intent, run accessibility checks, and produce fix-ready review notes — traced against a real review of this site's own article page.
Read articleDesign Critique Loops With Agents
A practical workflow for turning agent critique from vague opinion into structured findings, evidence, severity, revision passes, and human design decisions.
Read articleDesign System Audits With Agents
A deep workflow for finding design-system drift across tokens, components, screenshots, copy, interaction states, and product meaning.
Read articleFour Agentic Design Workflows in Production: What Actually Happened
Four real agentic design workflows traced from their own repositories — an editorial site, a multi-agent book pipeline, a book-to-video pipeline, and the design system underneath the site — with the timelines git can prove, the configs that did the steering, the failures the gates caught, and the patterns that repeat across all four.
Read article