adversarial-ux-test

Simulate a hostile user to triage app usability findings into RED, YELLOW, WHITE, or GREEN.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill adversarial-ux-test-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill adversarial-ux-test-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you uncover genuine usability friction by testing your product as a difficult, tech-resistant persona and separating real issues from complaint noise.

Core Features & Use Cases

  • Persona-driven testing: Simulate a stubborn, low-tech user so you can see where first impressions, terminology, and navigation break down.
  • Pragmatic triage: Sort findings into real UX bugs, low-priority edge cases, feature ideas, or plain resistance to change.
  • Actionable reporting: Turn the most important issues into ticket-ready notes with clear impact, quotes, and suggested fixes.

Quick Start

Run an adversarial UX test on your staging app as a grumpy first-time user and report the biggest friction points.

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 usability friction in my staging app before launch?

To find usability friction before launch, simulate a hostile, tech-resistant user navigating first-time flows and core workflows. This approach separates actionable bugs from complaint noise, identifying real issues with navigation, readability, and error recovery.

What is adversarial UX testing and how does it work?

Adversarial UX testing simulates a stubborn, low-tech persona interacting with a product to expose where terminology and navigation break down. It works by capturing screenshots and console errors, then triaging findings into actionable bug reports.

How do I triage UX testing findings into actionable bug reports?

Triage UX testing findings by categorizing them into RED, YELLOW, WHITE, or GREEN severity levels. This pragmatic sorting separates real UX bugs from low-priority edge cases and feature ideas, turning critical issues into ticket-ready notes with impact and suggested fixes.

Can I run UX testing on deployed products or is it only for staging?

You can run UX testing on both staging and deployed products. The testing applies to first-time flows, core workflows, error recovery, readability, navigation, and paywall checks across either environment using browser-based testing.

What's the best way to test paywall friction for first-time users?

The best way to test paywall friction is by simulating a grumpy first-time user navigating towards premium features. This persona-driven testing captures real resistance and identifies confusing terminology or navigation breakdowns at the paywall.

Why does separating complaint noise from real UX bugs matter during testing?

Separating complaint noise from real UX bugs matters because it prevents development teams from chasing feature ideas or edge cases. Pragmatic triage ensures only genuine usability friction impacting first-time users becomes ticket-ready output.