메뉴
Write a value proposition that connects what a product does to what a user gets. Use whenever the user mentions value prop, value proposition, customer value, benefit statement, or needs to articulate the value of their product in customer terms.
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 | value-prop-writing |
| description | Write a value proposition that connects what a product does to what a user gets. Use whenever the user mentions value prop, value proposition, customer value, benefit statement, or needs to articulate the value of their product in customer terms. |
a value proposition translates from product to user. it answers: "what do you do, and why should i care?"
for [audience], [product] is [category] that [outcome].
unlike [alternative], we [point of differentiation].
simple. it works because it carries audience, function, outcome, and differentiation.
write to one. you can have multiple value props for different audiences, but each one is written to one.
the user-facing result, not the feature.
what's really different. not what your team wishes were different.
words your audience uses, not words your team uses. if your audience says "deals", don't say "opportunities".
a single page often needs three layers:
what the value prop is in its sharpest form.
unpacks the hero. answers "tell me a little more".
concrete capabilities, integrations, customer outcomes, or capabilities that make the support paragraph believable.
example:
hero
"the spreadsheet built for product teams"
support
"product objects, not rows. shareable links, not access requests. extensible with code when spreadsheets stop being enough. built by people who got tired of pretending."
proof
- 8 of the top 20 product companies use it
- integrates with [list]
- average team saves [X hours per week]
- the founders shipped [specific past product]
if you serve more than one audience, write one value prop per audience and align them under a common hero. they should sound like variants of the same brand, not different companies.
audience
who: [specific]
what they're trying to do: [job]
what they try today: [alternative]
what bothers them about that: [pain]
hero (one line)
[value prop]
support (one paragraph)
[expanded]
proof (bullets)
[evidence]
variants
for [audience A]: [hero + support]
for [audience B]: [hero + support]
what we don't say
claims we could make but won't (e.g. promising what we can't deliver, or speaking to audiences we don't actually serve)