ais-ux-visual-evidence

Collect and verify UI visual and accessibility evidence with Playwright, axe, and Storybook.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-ux-visual-evidence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ais-ux-visual-evidence
Source: https://github.com/AIS-Commercial-Business-Unit/CBU_Specify/tree/main/Skills/ais-ux-visual-evidence
Command: npx skills add https://github.com/AIS-Commercial-Business-Unit/CBU_Specify --skill ais-ux-visual-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps ensure that UI implementations match the approved design and satisfy accessibility and responsive behavior expectations, reducing manual checks and potential compliance issues.

Core Features & Use Cases

  • Evidence Collection: Collect and plan screenshots, responsive checks, accessibility scans, and visual parity notes.
  • Design Source Matching: Compare UI implementation against approved design sources.
  • Accessibility Checks: Run automated checks for accessibility compliance.
  • Responsive Testing: Ensure UI is responsive across different viewports.
  • Use Case: When developing a new feature, use this Skill to collect evidence that the UI matches the design and meets accessibility standards before moving forward.

Quick Start

Use the ais-ux-visual-evidence skill to collect visual evidence for the "Feature X" implementation.

Frequently Asked Questions about ais-ux-visual-evidence

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

FAQPage Schema
How do I collect visual evidence to verify UI implementation against approved designs?

Collect visual evidence by capturing screenshots and generating parity notes to verify UI implementation matches approved design sources. This ensures the final interface meets the expected design specifications accurately before moving forward.

How do I run automated accessibility checks on my UI components?

Run automated accessibility checks using axe to scan your UI components for compliance issues. This identifies violations against accessibility standards, ensuring your UI implementation satisfies necessary requirements before moving forward.

What do I need to perform responsive testing across different viewports?

Perform responsive testing by checking the UI implementation across different viewports using Playwright. You need active feature directories and approved design specifications available to accurately compare responsive behavior against expected layouts.

Can I use Storybook to verify visual parity for my feature implementation?

Yes, Storybook works with this verification process to isolate and verify visual parity for your feature implementation. It allows you to capture visual evidence and compare components against approved design sources accurately.

Why does UI verification require active feature directories?

UI verification requires active feature directories because the process needs access to the actual implementation code and assets to run accessibility scans and capture accurate screenshots. Without these directories, comparing the UI against design specifications is impossible.