Research
Run a fresh UX research scan for the product the user specifies.
Focus on current, evidence-backed user problems. Prioritize logged-in product experience, self-serve flows, onboarding, docs/help, developer experience, support friction, and product workflows.
Critical Overrides
User Context
Before starting, load $product-design-user-context and run its preflight script when local shell access is available.
Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant.
Do not inspect every saved reference. Inspect only what the current task needs.
Contract
- Restate the product, audience, time horizon, and research scope before scanning.
- Use public sources by default. Use internal sources when the connectors are available and the user request allows it.
- Cite sources wherever available.
- Separate observed evidence from inference.
- Do not overclaim from anecdotes.
- Do not return a dump of complaints. Tell a clear product story.
- Say clearly when source access is missing or weak.
Workflow
Restate the research scope.
Search public sources:
- Reddit
- X/Twitter
- Hacker News
- Stack Overflow
- GitHub issues/discussions
- forums, blogs, reviews, YouTube comments, and developer communities where relevant
- Search internal sources when available:
- Slack
- Gong
- Notion
- Google Drive/docs
- Linear/Jira/GitHub
- support or CRM notes if available
Cluster evidence into the highest-signal UX problems.
Separate:
- product UI/workflow friction
- docs/help friction
- onboarding friction
- account, billing, permissions, or setup friction
- developer/API/SDK friction
- reliability/performance issues
- feature requests
Rank problems by severity, frequency, confidence, and product leverage.
Tell a clear product story.
Output
Default to an in-chat research brief unless the user asks for another format.
Include:
- Executive read: the core story in 5-7 sentences.
- Ranked UX problems: for each problem, include the problem, user goal, surface, what breaks, evidence, severity, frequency signal, confidence, and recommended product move.
- Source map: what was searched, what each source contributed, and where signal was weak.
- Opportunity map: group recommendations into fix this week, fix this quarter, and needs deeper research.
Rules
- Use citations wherever available.
- Do not overclaim from anecdotes.
- Separate loud complaints from frequent problems.
- Separate UX friction from missing features.
- Separate reliability/performance issues from UX workflow issues.
- Mark internal-only evidence separately from public evidence.
- Keep the brief sharp, specific, and easy to consume.
1---2name: product-design-research3description: Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.4---56# Research78Run a fresh UX research scan for the product the user specifies.910Focus on current, evidence-backed user problems. Prioritize logged-in product experience, self-serve flows, onboarding, docs/help, developer experience, support friction, and product workflows.1112## Critical Overrides1314- Refer to the Plugin router [$product-design](../product-design/SKILL.md) before proceeding.15- Follow [$critical-overrides](../../references/critical-overrides.md).1617## User Context1819Before starting, load [$product-design-user-context](../product-design-user-context/SKILL.md) and run its preflight script when local shell access is available.2021Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant.2223Do not inspect every saved reference. Inspect only what the current task needs.2425## Contract2627- Restate the product, audience, time horizon, and research scope before scanning.28- Use public sources by default. Use internal sources when the connectors are available and the user request allows it.29- Cite sources wherever available.30- Separate observed evidence from inference.31- Do not overclaim from anecdotes.32- Do not return a dump of complaints. Tell a clear product story.33- Say clearly when source access is missing or weak.3435## Workflow36371. Restate the research scope.38392. Search public sources:4041- Reddit42- X/Twitter43- Hacker News44- Stack Overflow45- GitHub issues/discussions46- forums, blogs, reviews, YouTube comments, and developer communities where relevant47483. Search internal sources when available:4950- Slack51- Gong52- Notion53- Google Drive/docs54- Linear/Jira/GitHub55- support or CRM notes if available56574. Cluster evidence into the highest-signal UX problems.58595. Separate:6061- product UI/workflow friction62- docs/help friction63- onboarding friction64- account, billing, permissions, or setup friction65- developer/API/SDK friction66- reliability/performance issues67- feature requests68696. Rank problems by severity, frequency, confidence, and product leverage.70717. Tell a clear product story.7273## Output7475Default to an in-chat research brief unless the user asks for another format.7677Include:7879- Executive read: the core story in 5-7 sentences.80- Ranked UX problems: for each problem, include the problem, user goal, surface, what breaks, evidence, severity, frequency signal, confidence, and recommended product move.81- Source map: what was searched, what each source contributed, and where signal was weak.82- Opportunity map: group recommendations into fix this week, fix this quarter, and needs deeper research.8384## Rules8586- Use citations wherever available.87- Do not overclaim from anecdotes.88- Separate loud complaints from frequent problems.89- Separate UX friction from missing features.90- Separate reliability/performance issues from UX workflow issues.91- Mark internal-only evidence separately from public evidence.92- Keep the brief sharp, specific, and easy to consume.
wukongnotnull