Skip to main content

brand-strategy-engine

Complete brand building and go-to-market system — from identity foundations through positioning, messaging, visual systems, and launch execution. Works for solopreneurs, startups, and established b...

ソース情報

リポジトリ
modbender/skill-library-mcp
ソースの最終更新活動
2026年3月6日 18:33
検出された SKILL.md の言語
英語
スター
12
フォーク
3

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
Brand Strategy Engine
description
Complete brand building and go-to-market system — from identity foundations through positioning, messaging, visual systems, and launch execution. Works for solopreneurs, startups, and established b...
# Brand Strategy Engine Complete brand building and go-to-market system — from identity foundations through positioning, messaging, visual systems, and launch execution. Works for solopreneurs, startups, and established businesses rebranding. --- ## Phase 1: Brand Discovery & Foundations Strategy before aesthetics. Every visual decision flows from these answers. ### 1.1 Brand Purpose Statement Answer in one sentence: **Why does this business exist beyond revenue?** Template: "We exist to [verb] [audience] by [method] so they can [outcome]." Examples: - "We exist to arm solo consultants with enterprise-grade tools so they can compete with agencies." - "We exist to simplify legal compliance for startups so founders can focus on building." **Test:** If you removed your company, would anyone notice? The answer reveals your true purpose. ### 1.2 Brand Values (Pick Exactly 3) More than 3 = forgettable. Fewer = too vague. Each value needs a **behavior** — what it looks like in practice. ```yaml brand_values: - value: "Radical Clarity" behavior: "We never use jargon. Every email, doc, and UI element passes the 'would my mom understand this?' test." anti_pattern: "Hiding behind buzzwords or complexity" - value: "Speed Over Perfection" behavior: "We ship MVPs in days, not months. We'd rather fix live than polish in private." anti_pattern: "Endless planning cycles, waiting for 'ready'" - value: "Skin in the Game" behavior: "We use our own products daily. Our pricing has a money-back guarantee." anti_pattern: "Recommending things we wouldn't buy ourselves" ``` ### 1.3 Brand Personality (The Archetype Method) Pick ONE primary archetype + ONE secondary flavor: | Archetype | Core Drive | Voice Tone | Best For | |-----------|-----------|------------|----------| | **Sage** | Knowledge, truth | Authoritative, measured | Consulting, education, analytics | | **Creator** | Innovation, vision | Inspiring, unconventional | Design, tech, creative agencies | | **Hero** | Mastery, achievement | Bold, confident, direct | Fitness, coaching, enterprise tools | | **Explorer** | Freedom, discovery | Adventurous, curious | Travel, startup tools, research | | **Rebel** | Revolution, disruption | Provocative, irreverent | Challenger brands, indie products | | **Caregiver** | Service, protection | Warm, reassuring | Healthcare, insurance, support | | **Ruler** | Control, stability | Premium, authoritative | Finance, luxury, enterprise | | **Everyman** | Belonging, honesty | Friendly, down-to-earth | Community tools, consumer products | | **Magician** | Transformation | Visionary, mystical | AI, wellness, life coaching | | **Jester** | Joy, humor | Witty, playful | Consumer apps, food, entertainment | | **Lover** | Intimacy, experience | Sensual, emotional | Fashion, beauty, hospitality | | **Innocent** | Simplicity, optimism | Clean, hopeful | Wellness, kids, organic products | **Output format:** ```yaml brand_personality: primary: "Rebel" secondary: "Sage" summary: "We challenge the status quo with data to back it up. Think punk rock meets MIT." we_are: ["bold", "evidence-driven", "unapologetic", "sharp"] we_are_not: ["corporate", "safe", "fluffy", "slow"] ``` ### 1.4 Competitive Landscape Map Before positioning, know the territory: ```yaml competitive_map: category: "[Your market category]" competitors: - name: "[Competitor A]" positioning: "[How they position themselves]" strengths: ["...", "..."] weaknesses: ["...", "..."] price_tier: "premium|mid|budget" brand_vibe: "[1-3 words]" - name: "[Competitor B]" # ... white_space: "[Where NO competitor plays — this is your opportunity]" category_conventions: "[What everyone in this space does — colors, language, promises]" our_contrarian_angle: "[How we'll deliberately break conventions]" ``` --- ## Phase 2: Positioning & Messaging ### 2.1 Positioning Statement (April Dunford Method) Fill in each element, then combine: ```yaml positioning: competitive_alternatives: "[What would customers use if you didn't exist?]" unique_capabilities: "[What you do that alternatives can't]" enabled_value: "[The measurable benefit those capabilities create]" best_fit_customers: "[Who cares MOST about that value — be specific]" market_category: "[The frame of reference that makes your value obvious]" ``` **Combined statement:** "For [best_fit_customers] who [pain point], [Brand] is the [market_category] that [unique_capabilities]. Unlike [competitive_alternatives], we [enabled_value]." **Positioning test — answer YES to all:** - [ ] Can a 12-year-old understand what you do from this? - [ ] Does it make clear who this is NOT for? - [ ] Would a competitor cringe reading it? (If not, it's too generic) - [ ] Does it contain a falsifiable claim, not just adjectives? ### 2.2 Messaging Architecture Three layers — never mix them: **Layer 1: Strategic Narrative (The Big Idea)** - One paragraph that frames the world as changing, positions you as the guide - Pattern: "The old way of [X] is broken because [shift]. Companies that [Y] are winning. [Brand] gives you [Z]." - Used in: About page, pitch deck, keynote openings **Layer 2: Value Propositions (3 Pillars)** ```yaml value_propositions: - pillar: "[Pillar Name]" headline: "[Benefit-driven, 8 words max]" subhead: "[How it works, 1 sentence]" proof: "[Specific stat, case study, or demo]" objection_it_handles: "[What skeptics say, and how this answers it]" - pillar: "..." - pillar: "..." ``` **Layer 3: Proof Points** For each value prop, stack evidence: - Customer quote (with name + company + result) - Metric ("43% faster onboarding") - Third-party validation (award, press mention, certification) - Demo/screenshot showing it in action ### 2.3 Ideal Customer Profile (ICP) ```yaml icp: demographics: company_size: "[range]" industry: ["...", "..."] revenue_range: "[range]" geography: ["..."] tech_stack: ["..."] # if relevant psychographics: biggest_pain: "[The thing that keeps them up at night]" current_workaround: "[How they solve it today — badly]" buying_trigger: "[What event makes them search for a solution?]" decision_maker: "[Title + what they care about]" influencer: "[Who researches options before the DM sees them]" budget_holder: "[Who signs the check]" anti_signals: # who NOT to target - "[Red flag 1 — e.g., 'wants custom everything']" - "[Red flag 2 — e.g., 'decision cycle > 6 months']" - "[Red flag 3 — e.g., 'budget under $X']" buying_journey: awareness: "[Where they first discover solutions — channels, searches]" consideration: "[What they compare — features, pricing, reviews]" decision: "[What tips them over — demo, trial, social proof, champion]" ``` ### 2.4 Tagline & Elevator Pitch **Tagline formulas (pick one, refine):** 1. **Verb + Outcome:** "Ship faster. Break nothing." 2. **Contrast:** "Enterprise power. Startup speed." 3. **Challenge:** "Stop guessing. Start knowing." 4. **Promise:** "From pipeline to paycheck in 14 days." 5. **Identity:** "Built for builders." **Tagline quality checklist:** - [ ] ≤6 words - [ ] No jargon or buzzwords - [ ] Works without context (on a billboard) - [ ] Implies a benefit, not a feature - [ ] Memorable — has rhythm, alliteration, or contrast **Elevator Pitch (30-second):** "You know how [target audience] struggles with [problem]? We built [Product] which [solution]. Unlike [alternative], we [key differentiator]. [Customer] used it to [specific result]." --- ## Phase 3: Brand Voice & Tone ### 3.1 Voice Guidelines Voice is constant. Tone adapts to context. ```yaml brand_voice: voice_in_3_words: ["direct", "warm", "sharp"] writing_rules: - "Short sentences. Max 20 words unless making a complex point." - "Active voice always. 'We built X' not 'X was built by us.'" - "Contractions: yes. 'We're' not 'We are.'" - "First person plural ('we') for company, 'you' for customer." - "No hedge words: 'very', 'quite', 'somewhat', 'a bit.'" - "Specific > vague. '$40K saved' not 'significant savings.'" - "One idea per paragraph. If you need a semicolon, make two sentences." vocabulary: use: ["ship", "build", "real", "prove", "earn", "move", "own"] avoid: ["leverage", "synergy", "streamline", "cutting-edge", "revolutionize", "ecosystem", "holistic"] tone_spectrum: celebration: "Bold, high-energy. Short punchy sentences. Exclamation marks OK (max 1 per paragraph)." education: "Clear, patient, structured. Use examples liberally. No condescension." error_state: "Honest, calm, action-oriented. Say what happened, what we're doing, when it'll be fixed." sales: "Confident, proof-heavy. Lead with outcomes, not features. Never desperate." support: "Warm, specific, fast. Mirror the customer's urgency level." ``` ### 3.2 Channel-Specific Adaptations | Channel | Tone Shift | Formatting | Length | |---------|-----------|------------|--------| | Website copy | Benefit-led, scannable | H2s, bullets, social proof | 50-100 words/section | | Email (marketing) | Conversational, CTA-focused | Short paragraphs, 1 CTA | 150-300 words | | Email (support) | Warm, solution-focused | Steps numbered, links inline | As short as possible | | Social (LinkedIn) | Professional, insight-led | Hook → Story → CTA | 150-300 words | | Social (Twitter/X) | Sharp, pithy, opinionated | Thread for depth, single for hooks | 280 chars or 5-8 tweet thread | | Blog/Content | Educational, comprehensive | H2/H3 structure, examples | 1500-2500 words | | Sales deck | Confident, customer-centric | Visuals > text, 6 words/slide | 10-15 slides | | Product UI | Minimal, action-oriented | Verb-first buttons, no jargon | 3-8 words | ### 3.3 Brand Voice Scorecard Rate any piece of content 1-5 on each dimension: | Dimension | 1 (Off-brand) | 5 (On-brand) | Weight | |-----------|--------------|--------------|--------| | Clarity | Jargon-heavy, confusing | Crystal clear, instant understanding | 25% | | Personality | Generic, could be anyone | Unmistakably us | 20% | | Specificity | Vague claims, adjective-heavy | Numbers, examples, proof | 20% | | Action | Passive, informational | Drives clear next step | 15% | | Consistency | Contradicts other brand comms | Reinforces brand story | 10% | | Audience-fit | Wrong level, wrong concerns | Speaks directly to ICP | 10% | **Score:** <60 = rewrite. 60-79 = revise. 80+ = publish. --- ## Phase 4: Visual Identity System ### 4.1 Color Palette **Primary (2 colors):** ```yaml colors: primary: main: "#[hex]" # Dominant brand color — used in logo, CTAs, headers accent: "#[hex]" # Secondary emphasis — used in highlights, hover states neutral: dark: "#[hex]" # Text, headings (near-black, never pure #000) medium: "#[hex]" # Secondary text, borders light: "#[hex]" # Backgrounds, cards white: "#[hex]" # Page background (often #FAFAFA, not pure white) semantic: success: "#[hex]" warning: "#[hex]" error: "#[hex]" info: "#[hex]" ``` **Color psychology quick guide:** - Blue = trust, stability (finance, enterprise, healthcare) - Green = growth, health (sustainability, wellness, finance) - Red/Orange = energy, urgency (food, entertainment, sales) - Purple = premium, creative (luxury, education, design) - Yellow = optimism, attention (consumer, youth, caution) - Black = premium, power (luxury, tech, fashion) - Teal = modern, approachable (SaaS, fintech) **Ratio rule:** 60% neutral / 30% primary / 10% accent ### 4.2 Typography ```yaml typography: heading: family: "[Font name]" weights: ["Bold (700)", "Semibold (600)"] style: "serif|sans-serif|display" body: family: "[Font name]"
GitHubで見る
この SKILL.md は非常に大きいため、SkillsMP では最初のセクションだけを表示しています。 GitHubで見る