정보
이 스킬은 스토리브랜드 프레임워크를 적용하여 개발자들이 브랜드 메시지를 명확히 하는 데 도움을 줍니다. 이 프레임워크는 고객을 주인공으로 위치시키는 내러티브를 구조화합니다. 웹사이트 카피 재작성, 피치 구성, 마케팅 자료 전반의 일관된 메시지 보장과 같은 작업에서 발동됩니다. 본 스킬은 브랜드가 고객의 이야기에 안내자로서 소통하는 방식을 변화시키는 데 중점을 둡니다.
빠른 설치
Claude Code
추천npx skills add wondelai/skills -a claude-code/plugin add https://github.com/wondelai/skillsgit clone https://github.com/wondelai/skills.git ~/.claude/skills/storybrand-messagingClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
StoryBrand Messaging Framework
Clarify your message so customers will listen. Customers don't buy the best products — they buy the ones they can understand the fastest.
Core Principle
The customer is the hero, not your brand. Your brand is the guide who helps the hero win. Position yourself as the hero and you compete with your customer; position yourself as the guide and you serve them.
Scoring
Goal: 10/10. Score any marketing copy or brand messaging by the Quick Diagnostic: 1 point per satisfied row (7 rows) plus up to 3 points for a one-liner that passes the cocktail party test (clear + repeatable in one hearing). Bands: 9-10 = customer is the hero, all three problem levels named, empathy + authority both shown, a 3-step plan, one obvious Direct CTA, and both success and failure stakes painted; 5-6 = SB7 partly applied but the internal problem, stakes, or CTA is missing; <=3 = brand-as-hero, feature-led, or no clear ask. Always state the current score and the specific changes needed to reach 10/10.
The SB7 Framework
Every compelling story follows the same pattern. Use this structure for all messaging:
1. A Character (The Hero)
Core concept: The customer is the hero, and your job is to define the ONE thing they want. Be specific about that single desire.
Why it works: Naming a desire opens a story gap — the distance between where the customer is and where they want to be. That tension pulls them in because they feel understood and want the gap closed.
Key insights:
- Focus on ONE desire per message — multiple desires dilute the story gap
- Tie the desire to survival (physical, financial, relational, or spiritual)
- Aspirational identity is powerful ("become the leader everyone respects")
- Different segments have different desires — write separate messaging per role, stage, and pain intensity
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage headline | Desire as outcome | "You want a beautiful smile" (not "our dentistry is excellent") |
| Landing page | One desire per page | "You want to retire early" |
| Segmentation | Tailor desire per segment | CEO: "Scale without chaos" vs. IC: "Do your best work without friction" |
Copy patterns:
- "You want [specific desire]..."
- "Imagine [aspirational identity]..."
- "What if you could [single clear outcome]?"
See: references/brand-script.md — fill out the BrandScript worksheet here when you need to draft all seven elements for a client from scratch.
2. Has a Problem
Core concept: Define the problem at three levels — external (tangible), internal (emotional), philosophical (the injustice) — and personify it with a specific villain.
Why it works: Companies sell solutions to external problems, but customers buy solutions to internal ones. Naming how the problem makes them feel — confused, overwhelmed, embarrassed — taps the emotional driver behind purchases.
Key insights:
- External: "my investments are scattered"; internal: "I feel overwhelmed"; philosophical: "people shouldn't need to be experts to retire well"
- A good villain is specific and relatable, not abstract — "Wall Street jargon designed to confuse you", not "complexity"
- Most brands stop at external problems, missing the internal ones that drive purchases
Product applications:
| Context | Application | Example |
|---|---|---|
| Website problem section | Name all three levels | External: "Scattered tools." Internal: "You feel overwhelmed." Philosophical: "Teams deserve clarity." |
| Email nurture | Lead with internal problem | "Tired of feeling like you're guessing?" |
| Ad copy | Personify the villain | "Stop letting confusing software steal your evenings." |
Copy patterns:
- "You're tired of [internal problem]..."
- "[Villain] has been keeping you from [desire]..."
- "It's not right that [philosophical problem]..."
3. And Meets a Guide
Core concept: Your brand is the guide, expressing empathy AND authority. Empathy shows you understand the pain; authority proves you can solve it.
Why it works: Customers are looking for a guide, not another hero — think Yoda, not Luke. Empathy makes them feel seen, authority (testimonials, logos, statistics) makes them feel safe, and together they create trust.
Key insights:
- Show empathy with "we understand" language; show authority with testimonials, client logos, statistics, awards
- Never make your origin story the centerpiece — that is hero behavior; brief, relevant credentials suffice
Product applications:
| Context | Application | Example |
|---|---|---|
| About page | Empathy first, then credentials | "We know what it's like to feel lost in financial jargon. That's why 10,000 families trust us." |
| Homepage social proof | Empathy headline + authority logos | "You're not alone. Join 5,000+ teams who found clarity." + client logos |
| Sales call | Open with empathy, close with authority | "I hear you — that sounds frustrating. Here's what we've seen work for teams like yours." |
Copy patterns:
- "We understand what it's like to [empathy statement]..."
- "We've helped [number] [customers] achieve [result]..."
- "You don't have to figure this out alone..."
See: references/sales-conversations.md — open when scripting a sales call or discovery session; covers discovery questions, objection handling, and full SB7 sales scripts.
4. Who Gives Them a Plan
Core concept: Give two plans: a Process Plan (3-4 steps showing how to work with you) and an Agreement Plan (commitments that remove risk).
Why it works: A clear plan acts as stepping stones across a creek — it reduces cognitive load and perceived risk. Without one, the path feels murky and customers stall.
Key insights:
- Process Plan: 3-4 numbered steps max, action verbs, memorable names ("1. Schedule a call. 2. Get a custom plan. 3. Start seeing results.")
- Agreement Plan: fear-removing commitments ("100% satisfaction guaranteed", "Cancel anytime")
- More than 4 steps overwhelms; numbering implies order and ease
Product applications:
| Context | Application | Example |
|---|---|---|
| Website plan section | 3-step process with icons | "1. Book a demo. 2. Get onboarded. 3. See results in 30 days." |
| Pricing page | Agreement plan reduces anxiety | "No contracts. Cancel anytime. 30-day money-back guarantee." |
| Email CTA | Reference the plan | "Getting started is simple — just three steps." |
Copy patterns:
- "Here's how it works: Step 1... Step 2... Step 3..."
- "Getting started is easy. Just [step 1]."
- "We promise [agreement plan commitment]."
5. And Calls Them to Action
Core concept: If you don't ask, they won't act. Use a Direct CTA (primary conversion action) plus a Transitional CTA (lower-commitment alternative).
Why it works: Customers act only when challenged to act. The transitional CTA keeps not-yet-ready people in your story until they are.
Key insights:
- Direct: "Buy Now", "Schedule a Call", "Get Started"; Transitional: "Download Free Guide", "Watch Demo", "Take the Quiz"
- Make the Direct CTA a visually prominent button (contrasting color) and repeat it down the page
- Use action language ("Get" not "Submit"); one obvious Direct CTA per page
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage | Direct CTA above the fold, repeated | "Get Started Free" in header and after each section |
| Blog post | Transitional CTA at the end | "Download our free checklist" |
| Single Direct CTA per message | One "Schedule Your Call" button |
Copy patterns:
- "Get [desired result] now."
- "Start your free [trial/demo/assessment] today."
- "Download your free [lead magnet]."
Ethical boundary: Never label a paid action as "free" or a Transitional CTA — the button text must match what happens on click.
See: references/website-wireframe.md — open when laying out a homepage or site; gives section-by-section structure and interior page templates.
6. That Helps Them Avoid Failure
Core concept: Show what happens if the customer does not act. Without stakes, there is no story.
Why it works: Humans are loss-averse — fear of losing motivates more than promise of gaining. A taste of what could go wrong moves customers from "interested" to "committed".
Key insights:
- A taste of consequence is enough — don't run a scare campaign
- Focus on opportunity cost, not punishment ("another year of feeling stuck")
- Pair failure with success messaging to create contrast
Product applications:
| Context | Application | Example |
|---|---|---|
| Landing page stakes section | Brief failure scenario before CTA | "Without a clear message, you'll keep losing customers to competitors they understand faster." |
| Email subject line | Light urgency | "Are you leaving revenue on the table?" |
| Sales conversation | Name cost of inaction | "What happens to your team if nothing changes in 6 months?" |
Copy patterns:
- "Don't let [negative outcome] happen when [solution] is this simple."
- "How long will you wait before [addressing the problem]?"
- "Every day without [solution], you're [cost of inaction]."
7. And Ends in Success
Core concept: Paint a vivid picture of life after working with you — in terms of status, completeness, and self-realization. Success closes the story gap opened in Element 1.
Why it works: People need to see the destination before starting the journey. Showing the transformation — not features — lets customers place themselves in that future and feel its pull.
Key insights:
- Status: "Become the go-to expert"; completeness: "Finally have financial peace of mind"; self-realization: "Be the leader you were meant to be"
- Show transformation with before/after comparisons and specific numbers
- Keep the success picture tangible, never vague or generic
Product applications:
| Context | Application | Example |
|---|---|---|
| Homepage success section | Specific after picture | "Imagine opening your inbox to qualified leads every morning — no cold outreach required." |
| Case study | Before/after with numbers | "Before: 2% conversion rate. After: 11% in 90 days." |
| Testimonials | Customers describe their success | "I finally feel like I know where every dollar is going." |
Copy patterns:
- "Imagine [specific success picture]..."
- "Join [number] [customers] who now [success outcome]..."
- "Finally, [completeness outcome] — without [old frustration]."
The One-Liner
A single sentence that explains what you do. Use it everywhere.
Formula: [Problem] + [Solution] + [Result]
Structure: "We help [CHARACTER] who struggle with [PROBLEM] to [SOLUTION] so they can [RESULT]."
Example: "We help small business owners who feel overwhelmed by marketing create a clear message so they can grow their revenue."
Test: Can someone repeat it after hearing it once? (the cocktail party test)
See: references/one-liners.md — open when drafting a one-liner; ~20 industry examples plus three alternative formulas (PSR, BAB, "We Exist Because").
Tone and Voice Guidelines
Keep brand voice consistent across channels while adapting to context.
Convey guide qualities: empathy ("We understand..."), authority ("In our experience..."), confidence ("Here's what works..."), helpfulness ("Let us show you...").
Avoid: hero language ("We're the best at..."), jargon (use the customer's words), condescension, and tentative weakness.
See: references/email-sequences.md — open when building a nurture or welcome sequence; SB7-mapped templates and subject-line formulas. See: references/multi-channel-consistency.md — open when adapting the message to a channel; social, video, podcast, and PR playbooks.
Common Mistakes
| Mistake | Why It Fails | Fix |
|---|---|---|
| Being the hero | Competes with customer | Position as guide |
| Multiple messages | Confuses people | One clear message per asset |
| Clever > clear | People don't decode messaging | Choose clarity always |
| Feature-focused | Customers buy transformation | Lead with outcomes |
| No clear CTA | No direction = no action | Ask for the sale |
| No stakes | No urgency = no motivation | Paint failure picture |
| Starting with "We" | Self-focused | Start with customer's problem |
Quick Diagnostic
| Question | If No | Action |
|---|---|---|
| Can a caveman grasp the offer in 5 seconds? | Message too complex | Simplify to one desire, one outcome |
| Is the customer clearly the hero? | Brand competes with customer | Rewrite from customer's perspective |
| Is the internal problem named, not just external? | Missing the emotional driver | Add "how it feels" language |
| Do you show empathy AND authority? | Trust gap | Add "we understand" + proof points |
| Is there a clear 3-step plan? | Path feels risky | Add Process + Agreement plans |
| Is there one obvious CTA? | Nobody acts | Add prominent, repeated Direct CTA |
| Do you show success AND failure stakes? | No narrative tension | Paint both outcome pictures |
Further Reading
For the complete methodology and worksheets:
About the Author
Donald Miller is the CEO of StoryBrand, which has helped over 10,000 businesses clarify their messaging. A New York Times bestselling author of Building a StoryBrand, Marketing Made Simple, and Business Made Simple, he distilled decades of narrative theory into the practical seven-part SB7 framework.
GitHub 저장소
자주 묻는 질문
storybrand-messaging Skill이란 무엇인가요?
storybrand-messaging은(는) wondelai이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 storybrand-messaging 관련 작업을 수행할 수 있게 합니다.
storybrand-messaging은(는) 어떻게 설치하나요?
이 페이지의 설치 명령을 사용하세요. storybrand-messaging을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.
storybrand-messaging은(는) 어떤 카테고리에 속하나요?
storybrand-messaging은(는) 메타 카테고리에 속합니다.
storybrand-messaging은(는) 무료로 사용할 수 있나요?
네. storybrand-messaging은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.
연관 스킬
이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
