Verified:GitHub

adversarial-ux-test

Roleplay a tech-resistant user to identify UX friction and generate RED/GREEN tickets.

4|Updated May 18, 2026

Search Tags:#accessibility #persona testing #ticket generation #ux testing #staging review #adversarial QA #pragmatism filter

Ready to run

npx skills add https://github.com/ZardLi1115/zedclaw --skill adversarial-ux-test-zardli1115

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/ZardLi1115/zedclaw/tree/main/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill adversarial-ux-test-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams uncover genuine UX friction by stress-testing a product with an adversarial, highly resistant persona, then filtering the output so only real, actionable problems become tickets.

Core Features & Use Cases

Adversarial persona testing: Roleplays a difficult, tech-resistant user to probe onboarding, core workflows, navigation, terminology, speed, and error recovery.
Pragmatism filter for signal quality: Classifies complaints into RED (real UX issues), YELLOW (valid but niche), WHITE (persona-noise), and GREEN (feature requests) so the team doesn’t drown in noise.
Actionable ticket creation: Produces up to 10 focused tickets (with persona-voice quotes and objective issue descriptions), plus screenshots of key pain points.

Quick Start

Run the adversarial UX test on your staging URL by telling the agent to roleplay the grumpy persona, complete the core workflow as that person, and produce a filtered report with tickets for RED and GREEN items.

Frequently Asked Questions about adversarial-ux-test

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

FAQPage Schema

How do I find real UX friction in my staging app before release?▼

To find real UX friction, you can run an adversarial UX test that roleplays a tech-resistant user navigating your core workflow, capturing screenshots and console errors to identify genuine pain points. It filters persona noise to surface only actionable issues.

What is the best way to convert user experience issues into actionable tickets?▼

The best way to convert user experience issues into tickets is to classify friction using a pragmatism filter, isolating RED real issues and GREEN feature requests, then generating up to 10 tickets with persona-voice quotes and objective descriptions.

Can I use persona testing to check onboarding validation and error recovery?▼

Yes, you can use persona testing to check onboarding validation and error recovery by having an agent roleplay a difficult user completing core workflows. This approach probes navigation clarity, terminology, speed, and empty-state friction.

How does a pragmatism filter improve UX testing reports?▼

A pragmatism filter improves UX testing reports by classifying complaints into RED real issues, YELLOW niche problems, WHITE persona noise, and GREEN requests. This prevents the team from drowning in noise and highlights genuine friction.

Does accessibility and readability testing work on deployed app URLs?▼

Yes, accessibility and readability testing works on deployed app URLs by performing persona-based browsing to evaluate content clarity and capture console errors. It identifies friction across empty states, paywalls, and core navigation flows.

What types of complaints are generated during an adversarial UX test?▼

During an adversarial UX test, complaint types generated include RED real UX issues, YELLOW valid but niche problems, WHITE persona noise, and GREEN feature requests. Only RED and GREEN items are converted into actionable tickets.