checklist-ux-review

Audit frontend UI implementations for visual states, accessibility, and responsive behavior.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/akourmaz/translate2 --skill checklist-ux-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checklist-ux-review
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/checklist-ux-review
Command: npx skills add https://github.com/akourmaz/translate2 --skill checklist-ux-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This checklist provides a structured method to verify that UI/UX implementations meet completeness criteria across visual states, accessibility, and responsive behavior, ensuring consistent quality.

Core Features & Use Cases

  • Visual state coverage for interactive components (default, hover, focus, active, disabled, loading, error, success)
  • Accessibility conformance checks (keyboard navigation, screen reader labels, color contrast, and responsive text sizing)
  • Responsive design validation across mobile, tablet, and desktop layouts during design QA and pre-release reviews

Quick Start

Run this checklist against the latest frontend build to confirm all visual states, accessibility, and responsive behavior.

Frequently Asked Questions about checklist-ux-review

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

FAQPage Schema
How do I audit frontend UI implementations for complete visual states?

Audit frontend UI implementations by applying a structured checklist to verify interactive component states like default, hover, focus, active, disabled, loading, error, and success. This enforces verification criteria across states with clear pass/fail signals before release.

What is the best way to verify accessibility conformance in a UI/UX review?

Verify accessibility conformance in a UI/UX review by checking keyboard navigation, screen reader labels, color contrast, and responsive text sizing. This structured checklist ensures frontend builds meet completeness criteria for consistent quality across accessibility checks.

How do I validate responsive design behavior across mobile, tablet, and desktop layouts?

Validate responsive design behavior by running design QA checks across mobile, tablet, and desktop layouts during pre-release reviews. This structured checklist confirms that UI/UX implementations maintain correct responsive behavior and layout consistency across breakpoints.

When do I need a structured checklist for pre-release UI reviews?

You need a structured checklist for pre-release UI reviews when verifying frontend code changes and design system updates to catch gaps before release. It applies structured verification criteria across visual states, accessibility, and performance to ensure complete UI/UX implementations.

Can I use this UI review checklist for design system updates and code changes?

Yes, you can use this UI review checklist for design system updates and frontend code changes. It applies structured verification criteria across visual states, accessibility, and responsive behavior to confirm complete UI/UX implementations and catch gaps before release.

Why does my UI implementation fail visual state coverage during design QA?

Your UI implementation fails visual state coverage during design QA when interactive components lack complete default, hover, focus, active, disabled, loading, error, or success states. The structured checklist enforces verification criteria with clear pass/fail signals to identify these gaps.