Adversarial Ux Test — Roleplay a hostile user to find and triage UX pain points
Adversarial Ux Test — Roleplay a hostile user to find and triage UX pain points
Start with meaning, then move to detail.
This lesson explains Adversarial Ux Test — Roleplay a hostile user to find and triage UX pain points as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Why This Works, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Adversarial Ux Test — Roleplay a hostile user to find and triage UX pain points without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Roleplay a hostile user to find and triage UX pain points
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Why This Works
Read this after the foundation, then connect it to the previous step.
- 04How to Use
Read this after the foundation, then connect it to the previous step.
- 05Step 1: Define the Persona
Read this after the foundation, then connect it to the previous step.
- 06Good Persona Example
Read this after the foundation, then connect it to the previous step.
- 07Bad Persona Example
Read this after the foundation, then connect it to the previous step.
- 08Step 2: Become the Asshole (Browse as the Persona)
Read this after the foundation, then connect it to the previous step.
- 09Step 3: The Rant (Write Feedback in Character)
Read this after the foundation, then connect it to the previous step.
- 10Step 4: The Pragmatism Filter (Critical — Do Not Skip)
Finish here to verify the result and special cases.
Copy only after you understand the effect.
"Run an adversarial UX test on [URL]"
"Be a grumpy [persona type] and test [app name]"
"Do an asshole user test on my staging site"[PERSONA NAME]'s Review of [PRODUCT]
Overall: [Would they keep using it? Yes/No/Maybe with conditions]
THE GOOD (grudging admission):
- [things even they have to admit work]
THE BAD (legitimate UX issues):
- [real problems that would stop them from using the product]
THE UGLY (showstoppers):
- [things that would make them uninstall/cancel immediately]
SPECIFIC COMPLAINTS:
1. [Page/feature]: "[quote in persona voice]" — [what happened, expected]
2. ...
VERDICT: "[one-line persona quote summarizing their experience]"Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.