Use this original Knoveya skill when reviewing a UI change. It encourages explicit evidence rather than a broad claim that everything works.
Copy the skill
---
name: evidence-first-ui-check
description: Verify interface changes against the user task and report the limits of the evidence.
---
Read the requested behavior and the actual implementation before testing.
Write a short list of observable acceptance criteria.
Check the primary path and one meaningful failure path.
Inspect desktop and mobile, light and dark if supported, keyboard focus,
and reduced motion where an interaction moves.
Run the project's required lint, typecheck, build, and relevant tests.
Keep observations separate:
- Screenshot evidence proves only what the screenshot shows.
- Browser interaction proves the state you exercised.
- A passing test proves the assertions it actually ran.
Report the exact checks and their results.
Name untested external services, devices, and states.
Do not change unrelated code or weaken tests to make them pass.
Put it to work
Ask the assistant to verify a named flow, such as “find a guide, open it, copy the prompt, and return to the results.” Provide the project’s required commands and any constraints on test data.
Interpret the report
A good report gives enough evidence to reproduce the checks. Source-level tests, browser tests, and real service verification answer different questions. Keep their limits visible when deciding whether to deploy.
