research-synthesis
Synthesize user research into themes, insights, and recommendations
What this skill does
# /design:research-synthesis > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Synthesize user research data into actionable insights. See the **user-research** skill for research methods, interview guides, and analysis frameworks. ## Usage ``` /design:research-synthesis $ARGUMENTS ``` ## What I Accept - Interview transcripts or notes - Survey results (CSV, pasted data) - Usability test recordings or notes - Support tickets or feedback - NPS/CSAT responses - App store reviews ## Output ```markdown ## Research Synthesis: [Study Name] **Method:** [Interviews / Survey / Usability Test] | **Participants:** [X] **Date:** [Date range] | **Researcher:** [Name] ### Executive Summary [3-4 sentence overview of key findings] ### Key Themes #### Theme 1: [Name] **Prevalence:** [X of Y participants] **Summary:** [What this theme is about] **Supporting Evidence:** - "[Quote]" — P[X] - "[Quote]" — P[X] **Implication:** [What this means for the product] #### Theme 2: [Name] [Same format] ### Insights → Opportunities | Insight | Opportunity | Impact | Effort | |---------|-------------|--------|--------| | [What we learned] | [What we could do] | High/Med/Low | High/Med/Low | ### User Segments Identified | Segment | Characteristics | Needs | Size | |---------|----------------|-------|------| | [Name] | [Description] | [Key needs] | [Rough %] | ### Recommendations 1. **[High priority]** — [Why, based on which findings] 2. **[Medium priority]** — [Why] 3. **[Lower priority]** — [Why] ### Questions for Further Research - [What we still don't know] ### Methodology Notes [How the research was conducted, any limitations or biases to note] ``` ## If Connectors Available If **~~user feedback** is connected: - Pull support tickets, feature requests, and NPS responses to supplement research data - Cross-reference themes with real user complaints and requests If **~~product analytics** is connected: - Validate qualitative findings with usage data and behavioral metrics - Quantify the impact of identified pain points If **~~knowledge base** is connected: - Search for prior research studies and findings to compare against - Publish the synthesis to your research repository ## Tips 1. **Include raw quotes** — Direct participant quotes make insights credible and memorable. 2. **Separate observations from interpretations** — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation. 3. **Quantify where possible** — "Most users" is vague. "7 of 10 users" is specific.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.