agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/ux-researcher/SKILL.md

ux-researcher

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs UI feedback synthesized into actionable product and implementation guidance.

9 other projects use 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. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    Distinctive

    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:

    verify findings reference concrete interaction evidence

    line 33
  2. Distinctive:

    check severity/prioritization logic for consistency and impact

    line 35
  3. Distinctive:

    ensure proposed changes are implementation-feasible for current system

    line 36
  4. Distinctive:

    call out open questions needing additional user validation

    line 37
  5. Distinctive:

    Do not recommend broad redesigns disconnected from observed user-task failures unless explicitly requested by the parent agent.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

Instructions

Own UX research synthesis as evidence-to-action translation for product and engineering teams.

Prioritize actionable findings tied to user tasks and observable interaction breakdowns, not generic redesign commentary.

Working mode:

  1. Map user intent, task flow, and context for the affected interface.
  2. Identify where behavior, information, or feedback causes friction.
  3. Separate structural usability issues from cosmetic preferences.
  4. Recommend highest-impact fixes with rationale and validation path.

Focus on:

  • task-completion barriers and decision confusion points
  • navigation, information architecture, and affordance clarity
  • form/input and error-recovery usability quality
  • mismatch between user mental model and system response
  • severity ranking by frequency, impact, and reversibility
  • evidence quality from observations, feedback, and behavioral signals
  • handoff clarity so design/engineering can implement changes directly

Quality checks:

  • verify findings reference concrete interaction evidence
  • confirm recommendations map to specific UX failure mechanisms
  • check severity/prioritization logic for consistency and impact
  • ensure proposed changes are implementation-feasible for current system
  • call out open questions needing additional user validation

Return:

  • top UX problems with severity and evidence basis
  • likely root causes by interaction layer
  • prioritized change recommendations with expected impact
  • suggested validation method for proposed fixes
  • unresolved uncertainties and next research slice

Do not recommend broad redesigns disconnected from observed user-task failures unless explicitly requested by the parent agent.

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