design-research

Synthesize user evidence and analytics into prioritized mobile product opportunities.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/zzafergok/tulpar --skill design-research-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-research
Source: https://github.com/zzafergok/tulpar/tree/main/.agent/skills/design-research
Command: npx skills add https://github.com/zzafergok/tulpar --skill design-research-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding what a mobile product should build and for whom is risky when teams rely on opinions or biased samples. This Skill structures evidence from interviews, analytics, store reviews, and competitive context into defensible, prioritized product opportunities. ## Core Features & Use Cases - Decision Framing: Define the product decision, target users, lifecycle stage, platform, business model, and what new evidence could change the decision. - Evidence Synthesis: Combine interviews, usability tests, analytics, support feedback, App Store or Play reviews, and competitive products while separating observation, interpretation, assumption, and recommendation. - Prioritization & Deliverables: Compare opportunities by user value, frequency, retention or revenue connection, confidence, and effort, then identify the smallest experiment to reduce key uncertainty. - Use Case: A product team sees rising churn after onboarding. Use this Skill to cluster funnel analytics, support tickets, and store reviews into opportunity statements with confidence levels and experiment ideas. ## Quick Start Use the design-research skill to synthesize our app store reviews, onboarding funnel analytics, and recent user interviews into a prioritized list of mobile product opportunities.

Frequently Asked Questions about design-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize mobile product opportunities from user research?▼

Compare opportunities by user harm or value, frequency, strategic relevance, retention or revenue connection, reach, confidence, effort, platform constraints, and reversibility. Then identify the smallest experiment that reduces the most important uncertainty.

What evidence sources should I use for mobile design research?▼

Use the smallest appropriate combination: interviews for motivations, usability tests for interaction problems, analytics for funnels and retention, support feedback for recurring pain, store reviews for directional signals, and competitors for market expectations.

Can I treat app store review frequency as user population data?▼

No. Store reviews and competitor observations are biased samples. Frequency in public comments should not be treated as population prevalence without supporting data from analytics or structured research.

How should research synthesis separate facts from assumptions?▼

Explicitly separate observation, interpretation, assumption, and recommendation. Cluster evidence into jobs, triggers, barriers, unmet needs, and desired outcomes while retaining contradictory cases and segment differences.

When should I use design-research instead of a general UX research skill?▼

Use design-research when deciding what a mobile product should build and for whom. Use a general UX researcher skill for research operations and a mobile UI/UX skill for visual design work.