skills.rest
sparkst
sparkstCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

QUX - UX Test Scenarios

Generate UX test scenarios for UI components covering happy paths, edge cases, errors, and accessibility.

Updated Jan 29, 2026
Search Tags:#accessibility#qa#wcag#ui components#test scenarios#aria#ux testing
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill qux-ux-test-scenarios-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: QUX - UX Test Scenarios
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/qshortcuts-support/skills/qux
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill qux-ux-test-scenarios-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually writing UX test scenarios for UI components is time-consuming and often misses edge cases, error states, and accessibility requirements, leaving gaps that surface as bugs in production. ## Core Features & Use Cases - Comprehensive Scenario Generation: Produces happy path, edge case, error state, and accessibility scenarios for any UI component with Given/When/Then structure. - WCAG 2.1 Accessibility Checks: Validates components against WCAG Level A/AA/AAA criteria, keyboard navigation, ARIA patterns, and color contrast using built-in reference checklists. - Structured Test Matrix Output: Documents scenarios with priority levels, browser/device coverage, and implementation notes in markdown files. - Use Case: After implementing a LoginForm component, run QUX to generate 10-15 test scenarios including validation errors, keyboard submission, screen reader announcements, and a prioritized test matrix ready for QA or automated test implementation. ## Quick Start Ask the AI to generate UX test scenarios for a specific component, for example: run QUX on src/components/LoginForm.tsx to produce a full test scenario document with accessibility checks.

Frequently Asked Questions about QUX - UX Test Scenarios

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

FAQPage Schema
How do I generate UX test scenarios for a React component?▼

Run QUX with the component path, such as QUX src/components/LoginForm.tsx. It analyzes the component's interactions and states, then outputs a markdown document with happy path, edge case, error, and accessibility scenarios plus a prioritized test matrix.

What accessibility standards does UX scenario testing cover?▼

The skill checks WCAG 2.1 at Level A and AA by default, with AAA available via the --wcag-level flag. It validates keyboard navigation, ARIA usage, color contrast ratios, and screen reader compatibility using the bundled wcag-checklist and aria-patterns references.

Can I generate scenarios for all modified components at once?▼

Yes, running QUX without arguments analyzes the git diff to find recently modified UI components and generates scenarios for each. You can also scope it to a task ID with --task=TASK-123.

Why does QUX report no UI components found?▼

This happens when the git diff contains no UI component changes. Specify the component path explicitly, for example QUX src/components/MyComponent.tsx, to bypass git-based discovery.

How do I reduce the number of generated test scenarios?▼

Use the --priority=P0,P1 flag to generate only high-priority scenarios for critical flows. You can also configure include and exclude patterns in a .qux.json file in the project root.

Related Skills

Explore More Software Engineering Skills→
LedgerHQLedgerHQ
615

ldls-web

Applies LDLS design system rules for @ledgerhq/lumen-ui-react components.

Official
Basic
xriuxriu
2

implement

Implements work from a spec or tickets using test-driven development.

Community
Intermediate
leejaedusleejaedus

code-review

Review code changes for security and quality issues with file:line recommendations.

Community
Advanced
cuellarfrcuellarfr
47

Accessibility Audit

Identify and report WCAG 2.2 conformance issues across pages, components, and flows.

Community
Advanced