Loop 036
The UI/UX Score Loop
A browser-based review that completes a real user task, scores each meaningful screen with the same checklist, improves weak spots, and retests the whole task.
Ready-to-use prompt
Copy the loop
Improve [user flow, such as signup] at [URL] until [completion criterion]. In a real browser, start each pass from fresh state—no saved login, cookies, or site data. Capture meaningful screens at the agreed sizes and modes, score them with one checklist, and improve the weakest safe area. Rerun the whole flow and keep only regression-free changes. Stop on success, two full passes with no gain, blocked access, or required approval. Return scores, screenshots, changes, and stop reason.
Verify / stop
The complete user task scores better without making another important screen worse.
The final dashboard shows the same entry point, fresh browser state, screen sizes, modes, scoring rubric, screenshots, score changes, and stop reason for every retained improvement.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this for a real task such as signup, login, onboarding, checkout, sharing, or creating and editing an item when the entire experience can be exercised in a browser and scored consistently.
How to run it
- Choose the user task, starting URL, success target, browser, clean-session rule, screen sizes, light or dark modes, screens to capture, and anything the agent must not change.
- Complete the task once without editing; capture normal screens plus meaningful loading, error, recovery, and success states, then score each with the same user-focused rubric.
- Improve the weakest safe area, start a new clean browser session, and repeat the entire task under the same conditions so before-and-after scores are comparable.
- Keep only changes that improve the target without hurting another important screen; stop on success, two passes with no gain, blocked access, or required approval.
Why it works
A clean browser session exposes problems that saved logins, cookies, and remembered settings can hide. Repeating the same task with the same scoring rubric makes the result comparable instead of relying on a vague impression that the interface feels better.
Implementation note
A flow means a user goal, such as signing up or checking out—not a guessed web address. A screen size is sometimes called a viewport; a mode may be light or dark. Judge what the user can see and do, not hidden console output.