메뉴
Synthesize user interviews, surveys, support tickets, or other research into themes and recommendations. Use whenever the user shares interview transcripts, survey responses, support data, customer research, or asks for synthesis of qualitative input.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Audit a brand's full identity (logo, typography, color, voice, visual language) for consistency, distinctiveness, and gap. Use when the user asks for a brand audit, identity review, brand health check, or wants to evaluate how a brand shows up across surfaces.
Plan a content calendar tied to product, brand, or marketing goals. Use when the user asks for a content plan, editorial calendar, content strategy, posting schedule, or wants to map content to themes and audiences over a period of time.
Write a sequence of emails for onboarding, nurture, sales, lifecycle, or launch. Use when the user asks for a drip campaign, email sequence, welcome series, onboarding emails, sales cadence, or any multi-email flow tied to a goal.
Design an a/b test or experiment including hypothesis, metrics, sample size, and analysis plan. Use whenever the user mentions a/b test, experiment, split test, multivariate test, or needs to design a test that produces a decision-quality result.
Audit a design or component for WCAG accessibility compliance. Use whenever the user mentions a11y, accessibility audit, WCAG check, contrast issues, keyboard navigation, screen reader support, focus order, or asks if a design is accessible.
Extract a brand voice guide from existing copy samples. Use whenever the user shares past copy and asks to define a voice, document a voice, create voice guidelines, or wants to make their existing voice teachable and repeatable.
| name | research-synthesis |
| description | Synthesize user interviews, surveys, support tickets, or other research into themes and recommendations. Use whenever the user shares interview transcripts, survey responses, support data, customer research, or asks for synthesis of qualitative input. |
raw research is data. synthesis is making it useful for decisions.
never synthesize from a sample if the full set is available. patterns you notice in the first three interviews are often artifacts of the order you read them in.
go through and tag statements. tags include:
keep the original wording. tag it. don't rewrite it yet.
group tagged statements by the shape of the underlying need, not the surface vocabulary. "i hate spreadsheets" and "i wish there was a faster way to track this" might be the same cluster.
for each cluster:
a theme is a cluster with a name. name it in the user's language, not your team's.
theme: [short label]
size: [N participants]
strength: [low / medium / high]
representative quotes: [2-3, attributed to participant id]
underlying job: [what they're trying to accomplish]
current workaround: [what they do today]
opportunity: [what a product could do here]
→ implication: [what this means for product decisions]
→ confidence: [low / medium / high based on sample and consistency]
a good synthesis lets a reader who wasn't in the interviews make the same product decision you would. if they'd reach a different conclusion, the synthesis isn't complete or the evidence isn't strong enough.