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
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- califa/skillstheir own version, first seen Nov 15, 2026
- redhoram/claude-landing-templatetheir own version, first seen Nov 7, 2026
- its-ash/skillstheir own version, first seen Nov 1, 2026
- omspradippatil/Claude-Skillstheir own version, first seen Nov 1, 2026
- juhovainio/ux-companiontheir own version, first seen Oct 25, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- nodetool-ai/nodetool★ 615same name
- cuellarfr/design-skills★ 94same name
- felvieira/claude-skills-fv★ 27same name
- justinqwerty/design-skills★ 9same name
- Gustavosilveira23/claude-design-skills★ 8same name
- pedroromeroluna/ai-first-product-skills★ 5same name
- omspradippatil/Claude-Skills★ 3same name
- califa/skills★ 2same name
- bedomax/webdesigner-agent★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- image-art-directionSkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- responsive-designSkill
- saas-dashboardSkill
- security-engineeringSkill
- super-admin-panelSkill
- testing-and-qualitySkill
- unslop-engineSkill
- visual-designSkill
- visual-regressionSkill
- website-architectureSkill
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
- Distinctive: line 10
Use when a design decision depends on uncertain user needs, confusing flows, or an unexplained drop-off and appropriate evidence can be …
- Distinctive: line 15
Do not present guesses as research findings.
- Distinctive: line 30
Ask about recent behavior and concrete tasks rather than leading users toward a preferred solution.
- Distinctive: line 43
Use analytics as behavioral evidence, not as a substitute for user understanding.
- Distinctive: line 48
Instead of asking, “Would you use this new dashboard?”, ask the participant to find a specific overdue invoice in a prototype, then observe …
- Distinctive: line 60
Check that the research question maps to a decision, the method is proportionate, evidence is clearly distinguished from inference, and the …
“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.
Files
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
- Turn the uncertainty into a neutral research question.
- Choose a proportionate method: support-ticket review, analytics, usability walkthrough, interview, or prototype test.
- Define recruitment and consent needs; minimize collection of personal information.
- Ask about recent behavior and concrete tasks rather than leading users toward a preferred solution.
- Separate observations, participant statements, interpretation, and recommendations.
- Identify sample limitations and confidence; do not generalize from a small or biased sample.
- 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.
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
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.

