agentleFS
adymireadymire/CraftLayer/skills/ux-research/SKILL.md

ux-research

Skill0 starsChanged 3 days agoMITView on GitHub

Use evidence and structured questions to understand users, tasks, usability problems, and product assumptions.

16 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

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 6

    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:

    Use when a design decision depends on uncertain user needs, confusing flows, or an unexplained drop-off and appropriate evidence can be …

    line 10
  2. Distinctive:

    Do not present guesses as research findings.

    line 15
  3. Distinctive:

    Ask about recent behavior and concrete tasks rather than leading users toward a preferred solution.

    line 30
  4. Distinctive:

    Use analytics as behavioral evidence, not as a substitute for user understanding.

    line 43
  5. Distinctive:

    Instead of asking, “Would you use this new dashboard?”, ask the participant to find a specific overdue invoice in a prototype, then observe …

    line 48
  6. Distinctive:

    Check that the research question maps to a decision, the method is proportionate, evidence is clearly distinguished from inference, and the …

    line 60

“Common” is measured: kept by at least 6 in 10 of the 14 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

UX Research

When to use

Use when a design decision depends on uncertain user needs, confusing flows, or an unexplained drop-off and appropriate evidence can be gathered.

When not to use

Do not present guesses as research findings. Do not recruit users, collect personal data, or run external studies without authorization.

Inputs and assumptions

Define the decision to make, target users, current evidence, constraints, privacy considerations, and whether research is exploratory or evaluative.

Workflow

  1. Turn the uncertainty into a neutral research question.
  2. Choose a proportionate method: support-ticket review, analytics, usability walkthrough, interview, or prototype test.
  3. Define recruitment and consent needs; minimize collection of personal information.
  4. Ask about recent behavior and concrete tasks rather than leading users toward a preferred solution.
  5. Separate observations, participant statements, interpretation, and recommendations.
  6. Identify sample limitations and confidence; do not generalize from a small or biased sample.
  7. Connect findings to a testable design decision and follow-up measure.

Decision rules

  • Research should change a decision; avoid research theater.
  • Protect participant confidentiality and follow applicable policies.
  • Report contradictory evidence and uncertainty.
  • Use analytics as behavioral evidence, not as a substitute for user understanding.

Example

Instead of asking, “Would you use this new dashboard?”, ask the participant to find a specific overdue invoice in a prototype, then observe where they look and what they expect to happen.

Common failures

  • Leading questions and hypothetical intent claims.
  • Treating stakeholder opinion or one participant as universal truth.
  • Recording sensitive information that is not needed.

Validation

Check that the research question maps to a decision, the method is proportionate, evidence is clearly distinguished from inference, and the recommendation includes limitations.

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.