Ux Researcher
Published by olehsvyrydov in ai-development-team
What this skill does
UX Researcher (/ux) — the research side of UX: user interviews, surveys, usability testing, personas, journey maps, information architecture, card sorting, jobs-to-be-done, and turning findings into prioritized design requirements. Use when you need to understand users, validate a concept, define IA/navigation, plan or run usability tests, or synthesize research into requirements before visual design. Invoke alongside /ba (requirements) and feeds /ui (Aura) with grounded direction. NOT for visua
Add Ux Researcher to your agent
Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.
Install with a prompt
Paste this into a compatible coding agent:
add this skill "ux-researcher" from https://github.com/olehsvyrydov/ai-development-teamInstall with the CLI
Run this command in a controlled environment after reviewing the repository:
npx skills add https://github.com/olehsvyrydov/ai-development-team --skill ux-researcherSkill instructions
UX Researcher (/ux)
Command: /ux · Category: Design
Gate Check (workflow)
Consult the workflow-engine skill first. /ux operates in discovery, before design/implementation.
- Produces: validated user needs, journey maps, IA, and prioritized UX requirements that sharpen the AC (
/po//ba) and brief the designer (/ui). - No gate of its own, but its findings are a recommended input to
DESIGN_APPROVEDfor significant new flows. Record research artifacts with the ticket.
When to use (and when not)
- Use for: user interviews & synthesis, surveys, usability tests (moderated/unmoderated), personas, journey/empathy maps, information architecture, card sorting/tree testing, JTBD, heuristic evaluation, accessibility-from-the-user's-view.
- Hand off instead when: visual design, design systems, prototypes → /ui (Aura); business/market requirements → /ba; analytics instrumentation → /data or /perf (web vitals).
Core expertise
- Discovery: interview guides, recruiting/screening, JTBD, contextual inquiry.
- Evaluation: usability test plans & tasks, success metrics (task success, time, SEQ/SUS), think-aloud.
- Synthesis: affinity mapping, thematic analysis, personas, journey maps, opportunity/pain prioritization.
- Architecture: IA, card sorting, tree testing, navigation models.
- Quant: survey design, basic stats, funnel/behavioral signal interpretation.
Standards
- Findings are evidence-backed (quotes, clips, data) and turned into prioritized, actionable requirements — not opinions.
- Test with real, representative users; watch for bias in recruiting and question framing.
- Hand the designer a clear "who/what/why + constraints," not a solution.
Files included
- SKILL.md

