adversarial-ux-test

Simulate a difficult adopter to identify UX friction and generate prioritized tickets.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill adversarial-ux-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adversarial-ux-test
Source: https://github.com/Rawgrowth-Consulting/rawclaw-agent/tree/main/optional-skills/dogfood/adversarial-ux-test
Command: npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill adversarial-ux-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roleplays a difficult, tech-resistant user to surface hidden UX friction and convert feedback into actionable tickets via a structured pragmatism filter.

Core Features & Use Cases

  • Roleplay adversarial personas to reveal terminology confusion, onboarding gaps, accessibility issues, and navigation friction.
  • Apply a pragmatic, multi-step filter to classify issues into actionable tickets (RED/GREEN/YELLOW/WHITE) and generate concrete fixes.
  • Produce a report that includes the persona rant and a prioritized ticket backlog suitable for product teams.

Quick Start

Run an adversarial UX test on your staging site to surface friction and generate actionable tickets.

Frequently Asked Questions about adversarial-ux-test

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

FAQPage Schema
What is adversarial UX testing and how does it expose user friction?▼

Adversarial UX testing roleplays difficult, tech-resistant personas to surface hidden user friction like navigation gaps and terminology confusion. It captures this friction as a persona rant and converts the feedback into actionable tickets.

How do I convert user feedback into prioritized tickets for my product backlog?▼

Convert user feedback into prioritized tickets by applying a pragmatism filter that classifies issues into RED, YELLOW, WHITE, and GREEN categories. This generates a structured, ticket-ready backlog suitable for product teams.

How do I run a persona-based UX test on a staging site?▼

Run a persona-based UX test by defining a difficult adopter persona and simulating their workflow on your staging site. The test identifies accessibility issues and onboarding gaps, producing a report with a persona rant and actionable tickets.

Can I use this to find onboarding and navigation friction before release?▼

Yes, roleplaying tough users on a staging site effectively identifies onboarding gaps, terminology confusion, and navigation friction before release. It applies a multi-step filter to classify these issues into actionable fixes.

What is the best way to categorize UX issues for software quality teams?▼

The best way to categorize UX issues is using a pragmatism filter that segments friction into RED, YELLOW, WHITE, and GREEN severity levels. This classification produces concrete fixes and a prioritized ticket backlog for software quality teams.

Why does standard UX testing miss terminology confusion and accessibility issues?▼

Standard UX testing often misses terminology confusion because it does not simulate highly tech-resistant users. Adversarial persona-based testing forces these hidden friction points to surface by roleplaying difficult adopters navigating the interface.