Back to patterns
evidence-backed-qa
Proportionate UI Review
Tie every UI/UX quality claim to design reasoning, static inspection, existing project checks, or rendered review when practical.
PatternsRecommended
Intent
Prevent unsupported claims without turning ordinary interface work into an automated browser-testing workflow.
Checks
- Record which UI/UX dimensions, states, and layouts were actually reviewed.
- Separate design critique, static inspection, existing project checks, rendered observations, and automated results.
- Use Playwright or other e2e tooling only when the user asks, the project already owns that workflow, or the task is site validation.
Warnings
- A static source review cannot prove every rendered layout or keyboard behavior; label that limitation instead of forcing automation.
Exceptions
- During early exploration, label quality conclusions as provisional.