Design QA Assistant
I built an AI-powered internal tool that compares Figma designs against developed screens, so designers spend time fixing issues, not finding them.
Role
Senior Product Designer
My Contributions
Design > Build > Ship
TIMELINE
1 week
TL;DR
Design QA was a manual, time-consuming step that lived entirely in a designer's head. I built an internal AI tool that automates it, upload a Figma screenshot and the developed screen, and it returns a structured list of visual discrepancies in seconds. What used to take 20–40 minutes per screen now takes under five, with consistent output every time.
UPLOAD Design > REVIEW > UPDATE Code
Identified and resolved a critical usability risk before development, avoiding a costly rebuild
PROBLEM
Manual QA was slow and inconsistent.
After every sprint, designers compared implemented screens to Figma frame by frame — checking spacing, type, and colour by eye. Repetitive, easy to miss things, and different every time.

Refined QA rules
Narrowed output to handoff-relevant issues like spacing, type, colour, components. Less noise.
Export rules
Share criteria with devs before QA, not after
Paste from clipboard
Cut the steps in half. Most screenshots already live on the clipboard, no file picker needed.
Refresh button
Re-run after a quick dev fix without leaving the tool or re-uploading.
SOLUTION
Manual QA was slow and inconsistent.
Upload a Figma screenshot and the developed screen. The tool runs a structured AI comparison and returns a prioritised list of discrepancies. Three steps, two uploads, one button.




ADOPTION AND IMPACT
Introduced mid-sprint, shared a link and ran a quick demo, no formal rollout.
Fast adoption because it fit the existing workflow designers were already taking screenshots and comparing manually.
Real use surfaced what wasn't working: output too broad, upload added friction, criteria needed to travel with the spec not after it.
Each pain point became an iteration.
↓ 60%
Time per QA check from ~60 min to under ~35 min
Consistency
Same output quality regardless of who runs it
