ux-research
Skill0 starsChanged 15 days agoMITView on GitHub
Ask about past behavior, not hypothetical intent; recruit the right users.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- adymire/CraftLayertheir 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 repository99 other files it gives its agents.
- accessibilitySkill
- api-designSkill
- api-docsSkill
- authenticationSkill
- authorizationSkill
- backup-recoverySkill
- career-planSkill
- changelogSkill
- ci-pipelinesSkill
- citation-checkSkill
- cloud-costSkill
- code-reviewSkill
- content-strategySkill
- context-budgetSkill
- conversion-optimizationSkill
- copy-editingSkill
- copywritingSkill
- coverage-strategySkill
- cryptographySkill
- data-qualitySkill
- data-visualizationSkill
- debuggingSkill
- decision-logSkill
- design-systemSkill
- dockerSkill
- documentationSkill
- e2e-testingSkill
- email-marketingSkill
- etl-designSkill
- experiment-designSkill
- experiment-methodsSkill
- fact-checkingSkill
- feedback-loopSkill
- flaky-testsSkill
- forecastingSkill
- fuzz-testingSkill
- go-concurrencySkill
- grant-writingSkill
- incident-opsSkill
- incident-responseSkill
- injection-defenseSkill
- integration-testingSkill
- interview-prepSkill
- job-fitSkill
- kubernetesSkill
- legacy-codeSkill
- linux-troubleshootingSkill
- literature-reviewSkill
- llm-evaluationSkill
- marketing-analyticsSkill
- meeting-facilitationSkill
- ml-evaluationSkill
- networkingSkill
- observabilitySkill
- onboardingSkill
- paid-adsSkill
- pandas-analysisSkill
- patent-searchSkill
- peer-reviewSkill
- portfolioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
3
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 17
Test the smallest risky assumption.
- Distinctive: line 31
No fabricated sources, data, or test results.
- Distinctive: line 32
If the task falls outside the method, say so and stop.
“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
Use
Apply this when the task matches the description. Keep the output decision-useful and mark unknowns.
Method
- Name the user, problem, and current alternative.
- List options with tradeoffs.
- Test the smallest risky assumption.
- Measure behavior and guardrails.
Focus: UX research.
Verification
- Prototype or test produced behavioral evidence.
- Guardrail metrics did not regress.
- State clearly what was not verified.
Boundaries
- This is a checklist, not proof of correctness.
- No fabricated sources, data, or test results.
- If the task falls outside the method, say so and stop.
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.