[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0N3TSETW58RBJ51Y1VTJ9":3,"skill-same:01M7F0N3TSETW58RBJ51Y1VTJ9":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0N3TSETW58RBJ51Y1VTJ9","ux-research-methods",null,"UX research methodology: usability testing protocols, user interviews, contextual inquiry, surveys, card sorting, and diary studies, plus synthesis frameworks including JTBD, journey mapping, and affinity diagramming. Use when planning a study, writing a discussion guide, or analyzing research data.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-research-methods\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ux-research-methods\ndescription: \"UX research methodology: usability testing protocols, user interviews, contextual inquiry, surveys, card sorting, and diary studies, plus synthesis frameworks including JTBD, journey mapping, and affinity diagramming. Use when planning a study, writing a discussion guide, or analyzing research data.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# UX Research Methods\n\n## Research Philosophy\n\nGreat design is grounded in evidence, not assumption. UX research exists to reduce the risk of building the wrong thing and to illuminate the gap between designer intent and user reality. Every design decision should trace back to user evidence — whether from direct observation, behavioral data, or validated heuristics.\n\n### The Research Hierarchy (adapted from NNG Group)\n\n1. **Behavioral data** (what users do) > **Attitudinal data** (what users say)\n2. **Qualitative research** (why) informs **quantitative research** (how much)\n3. **Generative research** (discover opportunities) precedes **evaluative research** (validate solutions)\n4. **Continuous discovery** (ongoing) outperforms **project-based research** (periodic)\n\n## Method Selection\n\n| Question type | Method | Typical sample |\n|---|---|---|\n| Workflows, workarounds, unarticulated needs | Contextual inquiry | 4-8 |\n| Motivations, mental models | Semi-structured interviews | 5-8 per segment |\n| Behavior over time | Diary study | 10-15 (dropout) |\n| Information architecture | Card sorting \u002F tree testing | 15-30 \u002F 50+ |\n| Can users complete the task? | Moderated usability test | 5 finds ~85% of issues |\n| Scaled task evidence | Unmoderated remote test | 10-20 |\n| Expert review, no users | Heuristic evaluation (3-5 evaluators) or cognitive walkthrough | n\u002Fa |\n| How many, how much | Surveys \u002F analytics | 100+ (400+ for segments) |\n| Which variant performs better | A\u002FB test | traffic for significance, define MDE first, 1-2 weeks min |\n\n## Research Operations\n\n### Planning a Research Study\n1. Define research questions (3-5 focused questions per study)\n2. Select appropriate method(s) based on questions and constraints\n3. Write a 1-page research plan: goals, method, participants, timeline, deliverables\n4. Recruit representative participants — screen rigorously for target criteria\n5. Prepare materials: discussion guide, task scenarios, consent forms\n6. Pilot test the protocol with 1-2 internal participants\n\n### Participant Recruitment\n- Screen for behavioral criteria, not just demographics\n- Include users with disabilities (minimum 1 per study for inclusive insights)\n- Offer fair compensation respecting participants' time and expertise\n- Maintain a participant panel for longitudinal research\n- Avoid \"professional testers\" — seek real target users\n\n### Ethical Research Practice\n- Obtain informed consent with clear explanation of data usage\n- Allow participants to withdraw at any time without consequence\n- Protect participant privacy and anonymize data\n- Never manipulate or deceive participants\n- Share findings back with participants when possible\n\n## AI-Assisted Analysis Rules\n\nTreat LLM themes and codes as a first pass only: review 100% of AI output for the first three studies, then spot-check 30-50%; trace every insight to a participant quote; the researcher authors the report; anonymize transcripts and get consent before any upload; disclose AI assistance.\n\n## Routing\n\n- **Choosing and running a study** — the full method selection matrix (discovery, evaluative, quantitative), moderator scripts, interview guides, contextual inquiry, diary studies, card sorting and tree testing, A\u002FB protocols, survey design, screener and consent templates, research ops: read `references\u002Fresearch-protocols.md`.\n- **Making sense of what you collected** — affinity diagramming, thematic coding, Jobs-to-Be-Done, journey maps, personas, SUS and significance tests, mixed methods, repositories, atomic research, AI-assisted synthesis with prompts and ethics: read `references\u002Fanalysis-frameworks.md`.\n\n## Cross-Referencing\n\n- For heuristic evaluation methodology, reference `nng-ux-heuristics`.\n- For accessibility research requirements, reference `accessibility-inclusive-design`.\n- For mobile-specific testing considerations, reference `mobile-ux-design`.\n- For design system validation, reference `design-systems-architecture`.\n- For UX metrics and measurement frameworks, reference `ux-metrics-measurement`.\n- For AI-specific research methods, reference `agentic-ai-generative-ux`.\n- Turning findings into design direction with structured critique: `design-critique-case-studies`\n\n## Key Sources\n\n- NNG Group: \"Which UX Research Methods\" and research methodology articles\n- Portigal, S. (2013). \"Interviewing Users\"\n- Krug, S. (2014). \"Rocket Surgery Made Easy\"\n- Sauro, J. & Lewis, J. (2016). \"Quantifying the User Experience\"\n- Arxiv: GenAI for UX Research (Dec 2025)\n- Arxiv: EvAlignUX — Evaluating AI Alignment in UX Research (Sep 2024)\n","# UX Research Methods\n\n## Research Philosophy\n\nGreat design is grounded in evidence, not assumption. UX research exists to reduce the risk of building the wrong thing and to illuminate the gap between designer intent and user reality. Every design decision should trace back to user evidence — whether from direct observation, behavioral data, or validated heuristics.\n\n### The Research Hierarchy (adapted from NNG Group)\n\n1. **Behavioral data** (what users do) > **Attitudinal data** (what users say)\n2. **Qualitative research** (why) informs **quantitative research** (how much)\n3. **Generative research** (discover opportunities) precedes **evaluative research** (validate solutions)\n4. **Continuous discovery** (ongoing) outperforms **project-based research** (periodic)\n\n## Method Selection\n\n| Question type | Method | Typical sample |\n|---|---|---|\n| Workflows, workarounds, unarticulated needs | Contextual inquiry | 4-8 |\n| Motivations, mental models | Semi-structured interviews | 5-8 per segment |\n| Behavior over time | Diary study | 10-15 (dropout) |\n| Information architecture | Card sorting \u002F tree testing | 15-30 \u002F 50+ |\n| Can users complete the task? | Moderated usability test | 5 finds ~85% of issues |\n| Scaled task evidence | Unmoderated remote test | 10-20 |\n| Expert review, no users | Heuristic evaluation (3-5 evaluators) or cognitive walkthrough | n\u002Fa |\n| How many, how much | Surveys \u002F analytics | 100+ (400+ for segments) |\n| Which variant performs better | A\u002FB test | traffic for significance, define MDE first, 1-2 weeks min |\n\n## Research Operations\n\n### Planning a Research Study\n1. Define research questions (3-5 focused questions per study)\n2. Select appropriate method(s) based on questions and constraints\n3. Write a 1-page research plan: goals, method, participants, timeline, deliverables\n4. Recruit representative participants — screen rigorously for target criteria\n5. Prepare materials: discussion guide, task scenarios, consent forms\n6. Pilot test the protocol with 1-2 internal participants\n\n### Participant Recruitment\n- Screen for behavioral criteria, not just demographics\n- Include users with disabilities (minimum 1 per study for inclusive insights)\n- Offer fair compensation respecting participants' time and expertise\n- Maintain a participant panel for longitudinal research\n- Avoid \"professional testers\" — seek real target users\n\n### Ethical Research Practice\n- Obtain informed consent with clear explanation of data usage\n- Allow participants to withdraw at any time without consequence\n- Protect participant privacy and anonymize data\n- Never manipulate or deceive participants\n- Share findings back with participants when possible\n\n## AI-Assisted Analysis Rules\n\nTreat LLM themes and codes as a first pass only: review 100% of AI output for the first three studies, then spot-check 30-50%; trace every insight to a participant quote; the researcher authors the report; anonymize transcripts and get consent before any upload; disclose AI assistance.\n\n## Routing\n\n- **Choosing and running a study** — the full method selection matrix (discovery, evaluative, quantitative), moderator scripts, interview guides, contextual inquiry, diary studies, card sorting and tree testing, A\u002FB protocols, survey design, screener and consent templates, research ops: read `references\u002Fresearch-protocols.md`.\n- **Making sense of what you collected** — affinity diagramming, thematic coding, Jobs-to-Be-Done, journey maps, personas, SUS and significance tests, mixed methods, repositories, atomic research, AI-assisted synthesis with prompts and ethics: read `references\u002Fanalysis-frameworks.md`.\n\n## Cross-Referencing\n\n- For heuristic evaluation methodology, reference `nng-ux-heuristics`.\n- For accessibility research requirements, reference `accessibility-inclusive-design`.\n- For mobile-specific testing considerations, reference `mobile-ux-design`.\n- For design system validation, reference `design-systems-architecture`.\n- For UX metrics and measurement frameworks, reference `ux-metrics-measurement`.\n- For AI-specific research methods, reference `agentic-ai-generative-ux`.\n- Turning findings into design direction with structured critique: `design-critique-case-studies`\n\n## Key Sources\n\n- NNG Group: \"Which UX Research Methods\" and research methodology articles\n- Portigal, S. (2013). \"Interviewing Users\"\n- Krug, S. (2014). \"Rocket Surgery Made Easy\"\n- Sauro, J. & Lewis, J. (2016). \"Quantifying the User Experience\"\n- Arxiv: GenAI for UX Research (Dec 2025)\n- Arxiv: EvAlignUX — Evaluating AI Alignment in UX Research (Sep 2024)\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fux-research-methods","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill ux-research-methods",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill ux-research-methods",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill ux-research-methods","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-research-methods\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fanalysis-frameworks.md","REFERENCE","参考文档",40271,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-research-methods\u002Freferences\u002Fanalysis-frameworks.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fresearch-protocols.md",34414,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fux-research-methods\u002Freferences\u002Fresearch-protocols.md",[58,64,71,78,85,92],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]