visual-feedback-ui-qa

Verifies runtime UI visual feedback and outputs P0/P1/P2 findings with evidence and minimal fixes.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Handy369/passto-pi-frame --skill visual-feedback-ui-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-feedback-ui-qa
Source: https://github.com/Handy369/passto-pi-frame/tree/main/skills/visual-feedback-ui-qa
Command: npx skills add https://github.com/Handy369/passto-pi-frame --skill visual-feedback-ui-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns uncertainty about “the UI looks right” into user-perceived, runtime evidence by verifying whether users can actually notice feedback, status changes, and interaction results.

Core Features & Use Cases

  • User-perceived visual feedback QA: checks whether the loading/empty/error/success/pending states and key interaction outcomes are clearly perceivable to users.
  • Structured findings output: produces P0/P1/P2 (or equivalent severity) issue lists with surface, user-visible evidence, impact, and the smallest actionable fix suggestion.
  • Scope guardrails: focuses on real runtime UI QA and avoids drifting into pure implementation, high-level design, or DevTools-style performance/network investigations.

Quick Start

Tell the agent to run the visual-feedback-ui-qa flow for the current runtime page and output a severity-tagged findings list with evidence and minimal fixes.

Frequently Asked Questions about visual-feedback-ui-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify UI visual feedback for loading and error states during acceptance testing?

You can verify UI visual feedback by running a runtime QA flow that checks whether loading, empty, error, success, and pending states are clearly perceivable to users. It confirms users notice interaction outcomes and status changes during acceptance testing.

What is the best way to document UI QA findings with severity levels?

The best way to document UI QA findings is generating structured P0/P1/P2 issue lists. Each finding includes the surface, user-visible evidence, impact, and the smallest actionable fix suggestion to guide development resolution.

Can I use runtime UI QA to check first-screen clarity and click feedback?

Yes, runtime UI QA can check first-screen clarity and click feedback. It verifies user-perceived visual feedback by confirming whether users can perceive interaction outcomes and status state changes after click, focus, and switch actions.

Does visual feedback UI QA cover performance debugging and network inspection?

No, visual feedback UI QA does not cover performance debugging or network inspection. It explicitly excludes pure implementation, pure design, and DevTools-style performance or network investigations to maintain focus on user-visible interaction evidence.

When do I need to run a visual feedback check for usability evidence?

You need to run a visual feedback check during acceptance scenarios where the main deliverable is UI usability evidence. It applies when confirming first-screen clarity and feedback after click, focus, or switch actions is required.