agentleFS
Sign inStart free
metaspartanmetaspartan/cybara/skills/adversarial-ux-test/SKILL.md

adversarial-ux-test

Skill38 starsChanged 5 months agoMITView on GitHub

Test an app as a difficult, low-patience persona, then filter complaints into actionable UX issues.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before demos, launches, onboarding changes, or major UI releases when the user wants friction found by a realistic hard-to-please …

    line 9
  2. Distinctive:

    Write the persona rant:

    line 28
  3. Distinctive:

    Test the core workflow before touring settings.

    line 40
  4. Distinctive:

    Do not create more than 10 tickets.

    line 41
  5. Distinctive:

    Do not turn "I hate computers" into product work unless it exposes a real accessibility or workflow issue.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adversarial UX Test

Use this before demos, launches, onboarding changes, or major UI releases when the user wants friction found by a realistic hard-to-please persona.

Workflow

  1. Define one persona:
    • Role, age range, technical comfort, core task, frustration triggers, and voice.
  2. Browse the app as that persona:
    • First impression.
    • Core workflow.
    • Error recovery.
    • Readability and accessibility.
    • Speed and perceived effort.
    • Terminology.
    • Navigation and return paths.
  3. Record evidence:
    • Screenshots for each major issue.
    • Console errors.
    • Network failures.
    • Click count for the core task.
  4. Write the persona rant:
    • In character, with concrete quotes and page references.
  5. Apply the pragmatism filter:
    • Red: real UX bug.
    • Yellow: valid but lower priority.
    • Green: feature request with strong value.
    • White: persona noise.
  6. Produce tickets only for Red and Green items.

Rules

  • One persona per session.
  • Test the core workflow before touring settings.
  • Do not create more than 10 tickets.
  • Separate entertaining persona feedback from objective product findings.
  • Do not turn "I hate computers" into product work unless it exposes a real accessibility or workflow issue.

Report Shape

Persona: <name and constraints>
Task: <core task>
Verdict: <would they keep using it?>

Persona feedback:
- "<quote>" - <what happened>

Filtered findings:
- RED: <issue, evidence, suggested fix>
- YELLOW: <issue>
- GREEN: <request>
- WHITE: <noise>

Tickets:
- <title> - <evidence> - <fix>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free