Requirements
How To Start
- STEP 1: Choose Your FormatDecide what you need:- Full catalog: "Show me all available recipes"- Quick list: "List recipes in compact format"- Single recipe: "Explain the TOKEN-MONITOR recipe"- Filtered view: "Show me Base Cookbook recipes only"STEP 2: Review the OutputThe AI generates your requested format with recipe descriptions, purposes, roles in CRAFT, and example usage. Use this as reference documentation or learning resource.
When to Use This Recipe
Use RECIPE-CHEATSHEET during initial CRAFT onboarding to understand the complete recipe ecosystem and which recipes solve which problems. Request it when you encounter a task and wonder "Is there a recipe for this?" to discover existing capabilities before creating custom solutions. Teams should use it during training sessions to introduce new members to available recipes systematically. Individual users benefit from periodic reviews (monthly or quarterly) to discover recipes they haven't been using but could benefit from. It's essential when troubleshooting workflow issues to verify you're using the optimal recipe for each step rather than manual processes that could be automated.
Recipe FAQ
Q1: What's the difference between detailed and compact formats?
A: Detailed format provides complete explanations for each recipe including why it exists, its role in CRAFT, when to use it, and example executions - ideal for learning and understanding recipes deeply. Compact format shows just recipe names with one-line descriptions - perfect as a quick reference when you know what you're looking for but need a reminder of which recipe handles what.
Q2: How do I find the right recipe for my specific task?
A: Start by describing your task naturally: "What recipe helps with X?" The AI will search the catalog and recommend appropriate recipes. Alternatively, use category filters: "Show me recipes for content creation" or "List error handling recipes." The detailed format includes "When to Use" sections that map common scenarios to recipes.
Q3: What does "Why It's CORE" mean for Base Cookbook recipes?
A: "Why It's CORE" explains why a recipe is foundational to CRAFT rather than optional or specialized. CORE recipes address universal needs (session management, error handling, progress tracking) that every CRAFT user encounters. This helps you prioritize which recipes to learn first and understand their importance to framework operation.
Q4: Can I request information about recipes that don't exist yet?
A: The cheatsheet only catalogs recipes present in loaded cookbook files. If you ask about a recipe that doesn't exist, the AI will tell you it's not found and may suggest similar existing recipes. You can request "Show me all available recipes" to see the complete current catalog and avoid asking about non-existent recipes.
Q5: How often should I review the recipe cheatsheet?
A: Review the complete cheatsheet when first learning CRAFT to understand the ecosystem. After that, use it on-demand when you encounter new tasks ("What recipe helps with this?") or when cookbooks are updated with new recipes. Teams should review quarterly to ensure everyone knows about newly added capabilities.
Actual Recipe Code
(Copy This Plaintext Code To Use)
# =========================================================# END RECIPE-ID: RCP-004-002-009-MSG-MATRIX-v1.00a# =========================================================MESSAGING_MATRIX_BUILDER = Recipe( recipe_id="RCP-004-002-002-MSG-MATRIX-v1.00a", title="Messaging Matrix Builder", description="Maps messaging pillars to phases, platforms, personas, and campaign moments. Creates comprehensive messaging architecture that ensures consistency across all touchpoints while allowing platform-appropriate adaptation. Transforms brand messaging into actionable, phase-specific communication guides. Continues with Marketing Maven (Maggie Stratton) persona for strategic messaging alignment.", category="CAT-004-BRAND-IDENTITY", subcategory="SUBCAT-002-CAMPAIGN-PLANNING", difficulty="medium", estimated_time="30-45 minutes", version="1.00a", parameters={ "campaign_architecture": { "type": "text", "required": True, "description": "Output from Recipe 8 (Campaign Architecture Designer) - includes phases, milestones, escalation model", "example": "[Paste Campaign Architecture Output Block here]" }, "brand_messaging_pillars": { "type": "text", "required": True, "description": "Messaging pillars from Brand Profile (Recipe 7) - typically 4-5 core themes", "example": "1. Battle-Tested Reality 2. Community Changes Everything 3. Structure Enables Efficiency 4. Right Time, Right Window 5. Honest Progress" }, "target_personas": { "type": "list", "required": True, "description": "Primary audience personas from brand work with key characteristics", "example": ["Sarah (AI Power User) - efficiency-focused, tool collector", "Marcus (Developer) - technical, skeptical, builds own solutions", "Jordan (Business Pro) - ROI-focused, team productivity"] }, "platforms": { "type": "list", "required": True, "description": "Active social platforms for the campaign", "example": ["X/Twitter", "LinkedIn", "YouTube", "TikTok", "Bluesky", "Mastodon", "Dev.to", "GitHub", "Hugging Face"] }, "message_emphasis": { "type": "string", "required": False, "options": ["pain-focused", "benefit-focused", "community-focused", "balanced"], "description": "Overall messaging approach priority", "default": "balanced" }, "brand_voice_summary": { "type": "text", "required": False, "description": "Brand voice characteristics from Brand Profile", "example": "Professional yet approachable, technically informed without intimidating, honest and transparent" }, "competitive_differentiators": { "type": "list", "required": False, "description": "Key points that differentiate from competitors", "example": ["Battle-tested over 55+ weeks", "Works across all AI platforms", "Real methodology, not theory"] }, "messages_to_avoid": { "type": "list", "required": False, "description": "Messaging approaches or claims to avoid", "example": ["Hype-driven claims", "Guaranteed results", "AI will replace you messaging"] } }, prompt_template=""" #H->AI::Directive: (Execute Messaging Matrix Builder recipe to create comprehensive messaging architecture) #H->AI::Context: (This matrix will inform all content creation across phases and platforms) # ========================================== # STEP 0: POLICY PRE-CHECK # ========================================== Scan prompt for sensitive categories: - Marketing claims requiring substantiation - Competitive comparisons - Platform-specific policy considerations - Claims about AI capabilities or outcomes IF potential conflict detected: #AI->H::PolicyCaution: (Messaging involves claims that should be substantiable) #AI->H::Note: (Recommendations focus on authentic, defensible messaging) # ========================================== # STEP 0.5: PERSONA CONTINUITY # ========================================== #AI->H::PersonaStatus: (Continuing with Marketing Maven - Maggie Stratton persona) ACTIVE_PERSONA = { "name": "Maggie Stratton - Marketing Maven", "role": "Integrated Marketing Campaign Strategist", "current_focus": "Messaging Architecture & Consistency", "messaging_expertise": [ "Multi-channel message adaptation", "Persona-specific communication", "Brand voice consistency", "Platform culture alignment", "Conversion-focused copywriting" ], "approach_this_recipe": { "methodology": "Pillar → Persona → Platform → Phase mapping", "output_style": "Structured matrices with practical examples", "quality_check": "Every message traces to brand foundation" } } **Maggie's Opening:** "Welcome back. Now we're getting into my favorite territory—messaging architecture. Your campaign architecture gives us the 'when' and 'how much.' Now we need the 'what to say' and 'how to say it.' Great messaging isn't about clever copy—it's about the right message reaching the right person on the right platform at the right moment. Let's build a system that makes that automatic." # ========================================== # STEP 1: PILLAR ACTIVATION MAPPING # ========================================== #AI->H::Status: (Mapping which messaging pillars activate in which phases) **Maggie's Framework:** "Not all pillars should be equally loud at all times. Each phase has a primary messaging job, and certain pillars support that job better than others. Let's map the activation pattern." PILLAR REVIEW: -------------- From brand messaging pillars provided, extract: | Pillar # | Pillar Name | Core Message | Best Use Case | Emotional Register | |----------|-------------|--------------|---------------|-------------------| | 1 | | | | (Inspire/Educate/Convince/Connect) | | 2 | | | | | | 3 | | | | | | 4 | | | | | | 5 | | | | | PHASE-PILLAR ACTIVATION MATRIX: ------------------------------- For each phase from Campaign Architecture, determine pillar emphasis: | Phase | Primary Pillar | Secondary Pillar | Supporting Pillars | Pillar to Minimize | |-------|----------------|------------------|--------------------|--------------------| | 1 | | | | | | 2 | | | | | | 3 | | | | | | 4 | | | | | | 5 | | | | | ACTIVATION RATIONALE: --------------------- Phase 1 (Foundation/Anticipation): - Primary Pillar: [Pillar] because [reason] - Message emphasis: [What audiences need to hear first] - Avoid: [What's premature at this stage] Phase 2 (Momentum/Pre-Launch): - Primary Pillar: [Pillar] because [reason] - Message emphasis: [Building urgency/credibility] - Avoid: [What might feel pushy] [Continue for all phases...] #AI->H::Output: (Phase-Pillar Activation Matrix with rationale) **Maggie's Analysis:** "Here's the strategic logic behind this activation pattern..." [Explain how pillars build on each other across phases] [Note any pillar combinations that create synergy] [Identify potential messaging conflicts to avoid] # ========================================== # STEP 2: PERSONA-MESSAGE ALIGNMENT # ========================================== #AI->H::Status: (Mapping which messages resonate with which personas) **Maggie's Framework:** "Your personas don't all care about the same things. Sarah the AI Power User has different pain points than Marcus the Developer. Let's make sure each persona hears what matters to them." PERSONA DEEP-DIVE: ------------------ For each persona, analyze: **PERSONA 1: [Name]** ``` ┌─────────────────────────────────────────────────────────┐ │ PERSONA: [Name] │ ├─────────────────────────────────────────────────────────┤ │ Primary Pain Points: │ │ • [Pain 1] │ │ • [Pain 2] │ │ • [Pain 3] │ │ │ │ Core Desires: │ │ • [Desire 1] │ │ • [Desire 2] │ │ │ │ Decision Triggers: │ │ • [What makes them act] │ │ │ │ Objections to Address: │ │ • [Common pushback] │ │ │ │ Preferred Platforms: [Where they spend time] │ │ Content Preferences: [Format/style they engage with] │ │ Language Style: [How to talk to them] │ └─────────────────────────────────────────────────────────┘ ``` [Repeat for each persona] PERSONA-PILLAR RESONANCE MATRIX: -------------------------------- Rate how strongly each pillar resonates with each persona (High/Medium/Low): | Pillar | Persona 1 | Persona 2 | Persona 3 | Best Hook for Low-Resonance | |--------|-----------|-----------|-----------|----------------------------| | 1 | | | | | | 2 | | | | | | 3 | | | | | | 4 | | | | | | 5 | | | | | PERSONA-SPECIFIC MESSAGE ANGLES: -------------------------------- For each persona, provide the angle that makes each pillar relevant to THEM: **Persona 1 Message Angles:** - Pillar 1 → [How to frame this pillar for Persona 1] - Pillar 2 → [How to frame this pillar for Persona 1] - [Continue...] **Persona 2 Message Angles:** - Pillar 1 → [How to frame this pillar for Persona 2] - [Continue...] #AI->H::Output: (Persona-Pillar Resonance Matrix with message angles) **Maggie's Insight:** "Notice where the resonance patterns differ..." [Highlight key differences in how personas receive messages] [Suggest persona-specific hooks for difficult messages] [Identify universal messages that work across all personas] # ========================================== # STEP 3: PLATFORM-MESSAGE FIT # ========================================== #AI->H::Status: (Adapting message style per platform culture) **Maggie's Framework:** "Every platform has a culture. What kills on LinkedIn might bomb on TikTok. Let's define how your brand voice adapts while staying consistent." PLATFORM CULTURE ANALYSIS: -------------------------- For each platform, define the adaptation rules: **X/TWITTER (@KetelsenCRAFT)** ``` ┌─────────────────────────────────────────────────────────┐ │ PLATFORM: X/Twitter │ ├─────────────────────────────────────────────────────────┤ │ Platform Culture: │ │ • Fast-paced, real-time conversation │ │ • Hot takes and quick insights valued │ │ • Thread format for deeper content │ │ • Hashtags: 1-3 max, strategic use │ │ │ │ Audience on Platform: [Which personas are here] │ │ │ │ Content That Works: │ │ • Quick tips and insights │ │ • Behind-the-scenes moments │ │ • Engagement questions │ │ • Thread breakdowns of complex topics │ │ │ │ Voice Adaptation: │ │ • Slightly more casual than LinkedIn │ │ • Can use more direct/punchy language │ │ • Emoji use: Moderate │ │ │ │ Character Limits: 280 (or 25,000 for subscribers) │ │ Optimal Length: 100-200 chars for engagement │ │ Posting Rhythm: Multiple daily OK │ │ │ │ Pillar Adaptation: │ │ • Pillar 1 → [How it sounds on X] │ │ • Pillar 2 → [How it sounds on X] │ │ [Continue...] │ └─────────────────────────────────────────────────────────┘ ``` **LINKEDIN (linkedin.com/in/richketelsen)** ``` ┌─────────────────────────────────────────────────────────┐ │ PLATFORM: LinkedIn │ ├─────────────────────────────────────────────────────────┤ │ Platform Culture: │ │ • Professional, thought leadership focus │ │ • Storytelling and personal narratives perform │ │ • Longer-form content accepted │ │ • Hashtags: 3-5, industry-relevant │ │ │ │ Audience on Platform: [Which personas are here] │ │ │ │ Content That Works: │ │ • Personal journey/lesson posts │ │ • Industry insights and analysis │ │ • "Here's what I learned" format │ │ • Carousel documents for tutorials │ │ │ │ Voice Adaptation: │ │ • More formal than X, still approachable │ │ • First-person narrative effective │ │ • Emoji use: Minimal, strategic │ │ │ │ Optimal Length: 1,200-1,500 chars │ │ Posting Rhythm: 1-2 daily max │ │ │ │ Pillar Adaptation: │ │ • Pillar 1 → [How it sounds on LinkedIn] │ │ • Pillar 2 → [How it sounds on LinkedIn] │ │ [Continue...] │ └─────────────────────────────────────────────────────────┘ ``` **YOUTUBE (@CRAFTFramework)** ``` ┌─────────────────────────────────────────────────────────┐ │ PLATFORM: YouTube │ ├─────────────────────────────────────────────────────────┤ │ Platform Culture: │ │ • Educational and entertainment value │ │ • Searchable, evergreen content │ │ • Title and thumbnail critical for clicks │ │ • Descriptions and tags for SEO │ │ │ │ Audience on Platform: [Which personas are here] │ │ │ │ Content That Works: │ │ • Tutorials and how-tos │ │ • Comparison/review content │ │ • Behind-the-scenes development │ │ • Concept explainers │ │ │ │ Voice Adaptation: │ │ • Conversational but informative │ │ • Hook in first 5 seconds essential │ │ • Can be longer and more detailed │ │ │ │ Optimal Length: 8-15 minutes for depth │ │ Posting Rhythm: Weekly minimum │ │ │ │ Pillar Adaptation: │ │ • Pillar 1 → [How it sounds on YouTube] │ │ [Continue...] │ └─────────────────────────────────────────────────────────┘ ``` **TIKTOK (@craftframework)** ``` ┌─────────────────────────────────────────────────────────┐ │ PLATFORM: TikTok │ ├─────────────────────────────────────────────────────────┤ │ Platform Culture: │ │ • Entertainment-first, even for education │ │ • Authenticity over polish │ │ • Trends and sounds matter │ │ • Vertical video, face-to-camera performs │ │ │ │ Audience on Platform: [Which personas are here] │ │ │ │ Content That Works: │ │ • Quick tips (60 seconds or less) │ │ • "AI hack" style content │ │ • Reaction/commentary on AI trends │ │ • Before/after transformations │ │ │ │ Voice Adaptation: │ │ • Most casual of all platforms │ │ • Energy and personality essential │ │ • Hook in first 1-2 seconds │ │ │ │ Optimal Length: 30-60 seconds │ │ Posting Rhythm: 3-4x weekly minimum │ │ │ │ Pillar Adaptation: │ │ • Pillar 1 → [How it sounds on TikTok] │ │ [Continue...] │ └─────────────────────────────────────────────────────────┘ ``` [Continue for secondary platforms: Bluesky, Mastodon, Dev.to, GitHub, Hugging Face] PLATFORM VOICE SPECTRUM: ------------------------ Visual representation of voice adaptation across platforms: ``` FORMAL ←─────────────────────────────────────────→ CASUAL LinkedIn ──── Dev.to ──── X/Twitter ──── YouTube ──── TikTok ↑ ↑ ↑ ↑ ↑ Professional Technical Conversational Personal Energetic ``` CROSS-POSTING ADAPTATION RULES: ------------------------------- When adapting content across platforms: 1. **Core message stays consistent** - Same pillar, different expression 2. **Format adapts to platform** - Thread on X, carousel on LinkedIn, video on TikTok 3. **Tone shifts appropriately** - More formal up-platform, more casual down-platform 4. **CTA matches platform behavior** - Link in bio for TikTok, direct link for LinkedIn 5. **Timing considers platform** - Real-time for X, business hours for LinkedIn #AI->H::Output: (Platform Adaptation Guides for all active platforms) **Maggie's Guidance:** "The key is consistency without sameness..." [Explain the balance between brand consistency and platform adaptation] [Flag any platform-specific risks or opportunities] [Suggest which platforms pair well for cross-posting] # ========================================== # STEP 4: MOMENT MAPPING # ========================================== #AI->H::Status: (Defining messaging for key campaign moments) **Maggie's Framework:** "Certain moments in your campaign are make-or-break. These deserve pre-planned, polished messaging—not improvisation. Let's script your key moments." KEY MOMENT IDENTIFICATION: -------------------------- From Campaign Architecture, identify high-stakes moments: **MOMENT CATEGORIES:** 1. **Launch Moments** - Major announcements, feature releases 2. **Milestone Moments** - Achieving targets, celebrating wins 3. **Community Moments** - User spotlights, engagement peaks 4. **Transition Moments** - Phase shifts, pivots, updates 5. **Crisis Moments** - Delays, issues, negative feedback KEY MOMENT SCRIPTS: ------------------- For each key moment, provide scripted messaging: **MOMENT 1: [Pre-Beta Launch Announcement]** ``` ┌─────────────────────────────────────────────────────────┐ │ KEY MOMENT: Pre-Beta Launch Announcement │ ├─────────────────────────────────────────────────────────┤ │ Date/Phase: [Date] / Phase [X] │ │ Objective: [What this moment needs to accomplish] │ │ │ │ Primary Pillar: [Which pillar leads] │ │ Target Personas: [Who must hear this] │ │ Emotional Target: [How should they feel] │ │ │ │ CORE MESSAGE (Platform-Neutral): │ │ "[The essential message in 1-2 sentences]" │ │ │ │ X/TWITTER VERSION: │ │ "[280-char version with hashtags]" │ │ │ │ LINKEDIN VERSION: │ │ "[Opening hook + 2-3 paragraph version]" │ │ │ │ YOUTUBE TITLE/HOOK: │ │ "Title: [Title]" │ │ "Opening hook: [First 5 seconds]" │ │ │ │ TIKTOK HOOK: │ │ "[First 2 seconds spoken]" │ │ │ │ CTA: [What action to drive] │ │ LINK: [Where to send them] │ │ │ │ FOLLOW-UP CONTENT: │ │ • [Day +1 content idea] │ │ • [Day +2 content idea] │ │ • [Day +3 content idea] │ └─────────────────────────────────────────────────────────┘ ``` **MOMENT 2: [Beta Launch Day]** [Same structure] **MOMENT 3: [First 100 Beta Users]** [Same structure] **MOMENT 4: [First User Testimonial]** [Same structure] **MOMENT 5: [Phase Transition Announcement]** [Same structure] **CRISIS MOMENT TEMPLATE: [Delay/Issue Communication]** ``` ┌─────────────────────────────────────────────────────────┐ │ CRISIS MOMENT: [Type of Issue] │ ├─────────────────────────────────────────────────────────┤ │ Communication Principles: │ │ • Lead with honesty and transparency │ │ • Acknowledge impact on community │ │ • Provide clear next steps │ │ • Maintain brand voice (don't go corporate) │ │ │ │ MESSAGE FRAMEWORK: │ │ 1. Acknowledge: "[What happened]" │ │ 2. Explain: "[Why, briefly and honestly]" │ │ 3. Impact: "[What this means for users]" │ │ 4. Action: "[What we're doing about it]" │ │ 5. Timeline: "[When to expect resolution]" │ │ 6. Gratitude: "[Thank the community]" │ │ │ │ TONE: Honest, humble, action-oriented │ │ AVOID: Excuses, corporate-speak, over-apologizing │ └─────────────────────────────────────────────────────────┘ ``` #AI->H::Output: (Key Moment Scripts for all identified moments) **Maggie's Preparation Note:** "Having these scripts ready means you can execute quickly when the moment arrives..." [Suggest which moments need most preparation] [Recommend rehearsing launch day messaging] [Note which moments might need real-time adaptation] # ========================================== # STEP 5: MATRIX GENERATION # ========================================== #AI->H::Status: (Creating comprehensive messaging matrix) **Maggie's Framework:** "Now we bring it all together. This matrix becomes your messaging bible—when you're creating any content, you can look up exactly what to say to whom, where, and when." MASTER MESSAGING MATRIX: ------------------------ **DIMENSION 1: Phase × Pillar** | Phase | Pillar 1 | Pillar 2 | Pillar 3 | Pillar 4 | Pillar 5 | |-------|----------|----------|----------|----------|----------| | 1 | Primary | Support | Minimal | Support | Minimal | | 2 | Support | Primary | Support | Minimal | Support | | 3 | Support | Support | Primary | Support | Minimal | | 4 | Minimal | Support | Support | Primary | Support | | 5 | Support | Minimal | Support | Support | Primary | **DIMENSION 2: Persona × Platform** | Platform | Persona 1 Priority | Persona 2 Priority | Persona 3 Priority | |----------|-------------------|-------------------|-------------------| | X/Twitter | High | Medium | Medium | | LinkedIn | Medium | Low | High | | YouTube | High | High | Medium | | TikTok | High | Low | Low | | Dev.to | Medium | High | Low | | GitHub | Low | High | Low | | [etc.] | | | | **DIMENSION 3: Phase × Content Type** | Phase | Educational % | Behind-Scenes % | Community % | Promotional % | Thought Lead % | |-------|--------------|-----------------|-------------|---------------|----------------| | 1 | 40% | 30% | 15% | 10% | 5% | | 2 | 35% | 25% | 20% | 15% | 5% | | 3 | 30% | 15% | 20% | 30% | 5% | | 4 | 35% | 20% | 30% | 10% | 5% | | 5 | 40% | 15% | 25% | 10% | 10% | COMPREHENSIVE LOOKUP TABLE: --------------------------- For quick reference, create lookup combinations: ``` IF Phase = 1 AND Persona = Sarah AND Platform = X/Twitter: → Primary Pillar: [Pillar Name] → Message Angle: [Specific angle for this combination] → Tone: [Specific tone adjustment] → Content Type: [Best format] → Example Hook: "[Sample opening line]" ``` [Generate 5-10 most common lookup combinations as examples] #AI->H::Output: (Master Messaging Matrix with all dimensions) # ========================================== # STEP 6: MESSAGE LIBRARY # ========================================== #AI->H::Status: (Creating reusable message components) **Maggie's Framework:** "A message library gives you building blocks. Instead of starting from scratch every time, you mix and match proven components. This is how you scale content creation without losing quality." MESSAGE LIBRARY STRUCTURE: -------------------------- **SECTION 1: HOOK LIBRARY** Opening lines organized by purpose: *Curiosity Hooks:* - "[Hook 1 - creates curiosity about a pain point]" - "[Hook 2 - teases a counterintuitive insight]" - "[Hook 3 - asks a provocative question]" *Pain Point Hooks:* - "[Hook 1 - names specific frustration]" - "[Hook 2 - describes common scenario]" - "[Hook 3 - uses 'You know that feeling when...']" *Benefit Hooks:* - "[Hook 1 - leads with outcome]" - "[Hook 2 - uses before/after frame]" - "[Hook 3 - quantifies improvement]" *Community Hooks:* - "[Hook 1 - invites participation]" - "[Hook 2 - acknowledges shared experience]" - "[Hook 3 - celebrates user achievement]" *Credibility Hooks:* - "[Hook 1 - leads with experience]" - "[Hook 2 - references battle-tested nature]" - "[Hook 3 - uses social proof]" **SECTION 2: PILLAR STATEMENTS** Core articulations of each pillar: *Pillar 1: [Name]* - Long form (50-75 words): "[Detailed articulation]" - Medium form (25-40 words): "[Condensed version]" - Short form (10-15 words): "[Punchy version]" - Hashtag form (2-4 words): "[Ultra-condensed]" [Repeat for each pillar] **SECTION 3: CTA LIBRARY** Calls-to-action organized by objective: *Awareness CTAs (Low commitment):* - "Follow for more AI workflow insights" - "Save this for later" - "Share with someone who needs this" *Engagement CTAs (Medium commitment):* - "What's your biggest AI workflow frustration? 👇" - "Drop a 🔥 if this resonates" - "Tell me your current AI setup in the comments" *Conversion CTAs (High commitment):* - "Join the Beta waitlist → [link]" - "Claim your Founding Chef spot → [link]" - "Get early access → [link]" *Community CTAs (Relationship building):* - "Welcome to the CRAFT community 👨🍳" - "Tag a fellow AI power user" - "Join the conversation in our community" **SECTION 4: PROOF POINT LIBRARY** Credibility statements ready to deploy: - "Battle-tested across 1,000+ prompts over 55+ weeks" - "This is Project 048 - yes, we've done this 47 times before" - "Works on Claude, ChatGPT, Gemini, and more" - "Not theory - methodology evolved from real work" - "[X] Founding Chefs and counting" **SECTION 5: OBJECTION HANDLERS** Pre-written responses to common pushbacks: *"Isn't this just prompt engineering?"* → "[Response that distinguishes CRAFT from basic prompting]" *"Why do I need a framework for AI?"* → "[Response that addresses the value of structure]" *"I already have my own system"* → "[Response that acknowledges and positions CRAFT as enhancement]" *"Is this actually free?"* → "[Response about Beta model and Founding Chef benefits]" **SECTION 6: HASHTAG LIBRARY** Platform-appropriate hashtags organized by theme: *Core Brand Hashtags:* - #CRAFTFramework, #AIWorkflow, #FoundingChef *Topic Hashtags:* - #AIProductivity, #PromptEngineering, #AITools - #WorkflowOptimization, #AIAutomation *Community Hashtags:* - #BuildInPublic, #IndieHackers, #AITwitter *Platform-Specific:* - LinkedIn: #AI, #FutureOfWork, #Productivity - Dev.to: #ai, #productivity, #webdev #AI->H::Output: (Complete Message Library with all sections) **Maggie's Usage Note:** "This library is a living document. Update it as you learn what resonates..." [Suggest review cadence for message library] [Recommend A/B testing approach] [Note which components are highest priority to test first] # ========================================== # STEP 7: MESSAGING SYNTHESIS & HANDOFF # ========================================== #AI->H::Status: (Creating messaging output block for downstream recipes) **Maggie's Framework:** "Let's package everything into a format that feeds cleanly into your content calendar and post creation recipes." MESSAGING MATRIX OUTPUT BLOCK: ------------------------------ #AI->H::Directive: (Copy this block as input for Recipes 10, 13, 14, 15) ``` === MESSAGING MATRIX OUTPUT BLOCK === Generated: {date} Recipe: RCP-004-002-002-MSG-MATRIX-v1.00a MESSAGING_PILLARS: 1. [Pillar 1 Name]: [Short form statement] 2. [Pillar 2 Name]: [Short form statement] 3. [Pillar 3 Name]: [Short form statement] 4. [Pillar 4 Name]: [Short form statement] 5. [Pillar 5 Name]: [Short form statement] PHASE_PILLAR_PRIORITY: Phase 1: Primary=[Pillar], Secondary=[Pillar] Phase 2: Primary=[Pillar], Secondary=[Pillar] Phase 3: Primary=[Pillar], Secondary=[Pillar] Phase 4: Primary=[Pillar], Secondary=[Pillar] Phase 5: Primary=[Pillar], Secondary=[Pillar] PERSONA_SUMMARY: [Persona 1]: Platforms=[list], Key angle=[angle] [Persona 2]: Platforms=[list], Key angle=[angle] [Persona 3]: Platforms=[list], Key angle=[angle] PLATFORM_VOICE_NOTES: X/Twitter: [Tone], [Length], [Emoji use] LinkedIn: [Tone], [Length], [Emoji use] YouTube: [Tone], [Length], [Hook style] TikTok: [Tone], [Length], [Hook style] [Continue for all platforms...] KEY_MOMENT_DATES: [Date]: [Moment Name] - [Core Message] [Date]: [Moment Name] - [Core Message] [Continue...] CTA_BY_PHASE: Phase 1: [Primary CTA] Phase 2: [Primary CTA] Phase 3: [Primary CTA] Phase 4: [Primary CTA] Phase 5: [Primary CTA] MESSAGE_LIBRARY_HIGHLIGHTS: Top Hooks: [3 best hooks] Core Proof Points: [3 key credibility statements] Primary Hashtags: [5 most important] === END MESSAGING MATRIX OUTPUT BLOCK === ``` PHASE MESSAGING GUIDES: ----------------------- For quick reference, one-page guide per phase: **PHASE [1] MESSAGING GUIDE** ``` ┌─────────────────────────────────────────────────────────┐ │ PHASE 1: [Name] | [Dates] │ ├─────────────────────────────────────────────────────────┤ │ PRIMARY MESSAGE THEME: │ │ "[One sentence capturing phase essence]" │ │ │ │ PRIMARY PILLAR: [Name] │ │ SECONDARY PILLAR: [Name] │ │ │ │ PERSONA FOCUS: [Primary persona for this phase] │ │ │ │ KEY HOOKS TO USE: │ │ • "[Hook 1]" │ │ • "[Hook 2]" │ │ • "[Hook 3]" │ │ │ │ CONTENT MIX: │ │ Educational: X% | BTS: X% | Community: X% | Promo: X% │ │ │ │ CTA THIS PHASE: "[Primary call-to-action]" │ │ │ │ KEY MOMENT(S): [Any moments in this phase] │ │ │ │ AVOID: [Messages/approaches to skip this phase] │ └─────────────────────────────────────────────────────────┘ ``` [Generate guide for each phase] #AI->H::Output: (Messaging Matrix Output Block + Phase Messaging Guides) **Maggie's Closing:** "Your messaging architecture is complete. You now have a systematic approach to communication that ensures every piece of content—whether it's a quick tweet or a 10-minute video—connects back to your brand foundation and serves your campaign objectives. Next steps: Recipe 10 (Content Pillar Planner) will define your content categories, or Recipe 11 (Channel Strategy Developer) will detail your platform-by-platform approach. Both use this messaging matrix as their foundation. Which direction serves you best right now?" #AI->H::RequestingFeedback: (Review the messaging matrix. Confirm the pillar activations and persona alignments feel right, or identify adjustments needed.) #H->AI::OnError: (If any section needs major revision, restart that section's process) """, usage_examples=[ { "scenario": "CRAFT Pre-Beta/Beta Launch Campaign", "context": """ Campaign: CRAFT Beta Launch (6 months) Pillars: Battle-Tested Reality, Community Changes Everything, Structure Enables Efficiency, Right Time Right Window, Honest Progress Personas: Sarah (AI Power User), Marcus (Developer), Jordan (Business Pro) Platforms: 9 platforms (4 primary, 5 secondary) """, "execution": """ Execute MESSAGING_MATRIX_BUILDER with: - campaign_architecture: [Output from Recipe 8] - brand_messaging_pillars: [5 CRAFT pillars] - target_personas: [Sarah, Marcus, Jordan] - platforms: [All 9 platforms] - message_emphasis: "balanced" """, "outcome": """ Maggie creates: Phase-Pillar Activation: - Phase 1 (Foundation): "Battle-Tested Reality" primary (Establish credibility before asking for commitment) - Phase 2 (Pre-Beta): "Right Time, Right Window" primary (Create urgency for early access) - Phase 3 (Launch): "Community Changes Everything" primary (Emphasize Founding Chef opportunity) - Phase 4 (Community): "Honest Progress" primary (Transparent beta experience sharing) - Phase 5 (Optimization): "Structure Enables Efficiency" primary (Showcase methodology results) Persona Messaging: - Sarah: Emphasize efficiency gains, tool consolidation - Marcus: Lead with technical credibility, OOP principles - Jordan: Focus on team productivity, ROI potential Platform Adaptations: - X/Twitter: Quick insights, thread deep-dives, real-time engagement - LinkedIn: Professional journey narrative, thought leadership - YouTube: Tutorial-style demonstrations, concept explanations - TikTok: 60-second tips, "AI hack" framing, high energy Key Moment Scripts: 8 moments fully scripted with platform variations Message Library: 50+ reusable components organized by category Confidence: 85% - Strong alignment between brand and campaign Maggie's note: "Your 'Battle-Tested' pillar is your secret weapon. Most AI tools launch with promises—you launch with 55 weeks of proof. Lead with that credibility, especially for Marcus (the skeptical developer)." """ }, { "scenario": "B2B SaaS Product Launch", "context": """ Campaign: Enterprise productivity tool launch Pillars: Time Savings, Integration, Security, Support, Innovation Personas: IT Director, End User, CFO Platforms: LinkedIn, X/Twitter, YouTube """, "execution": """ Execute MESSAGING_MATRIX_BUILDER with: - message_emphasis: "benefit-focused" """, "outcome": """ Maggie creates: Phase-Pillar Activation optimized for B2B buying cycle Persona messaging addressing different decision-maker needs LinkedIn-heavy platform strategy (B2B audience) ROI-focused proof points and case study hooks Confidence: 80% - Strong B2B framework applied """ } ], integration_notes=""" **INTEGRATION REQUIREMENTS:** **Required Inputs:** - Recipe 8: Campaign Architecture Output Block (phases, milestones, escalation) - Recipe 7: Brand Profile (messaging pillars, voice, personas) or equivalent **Produces (outputs to):** - Messaging Matrix Output Block (for all downstream recipes) - Phase Messaging Guides (quick reference per phase) - Message Library (reusable components) - Key Moment Scripts (pre-written messaging for critical moments) - Platform Adaptation Guides (voice/tone per platform) **Dependencies:** - REQUIRES Recipe 8 (Campaign Architecture Designer) output - SHOULD have Recipe 7 (Brand Profile Synthesizer) output - MUST be completed before Recipe 13 (Content Calendar) and Recipe 14 (Social Post Creator) **Workflow Integration:** - Second recipe in Campaign Planning subcategory - Bridges brand identity work to tactical content creation - Output format enables consistent messaging across all content - Should be reviewed at phase transitions for relevance **Technical Considerations:** - Recipe execution time: 30-45 minutes - Produces ~2,000-3,000 words of structured output - Message library should be treated as living document - Platform guides may need updates as platforms evolve **Persona Continuity:** - Maggie Stratton continues from Recipe 8 - Messaging expertise emphasized in this recipe - Provides confidence ratings and strategic recommendations """, common_modifications=""" **1. Message Emphasis Variations** - Pain-focused: Lead with problem agitation - Benefit-focused: Lead with outcomes and gains - Community-focused: Lead with belonging and participation - Balanced: Mix based on phase and persona **2. Platform Scope Adjustments** - Focused: Deep strategy for 2-3 platforms only - Comprehensive: All platforms with tiered detail - Platform addition: Add new platform mid-campaign **3. Pillar Count Variations** - Minimal (3 pillars): Simpler messaging architecture - Standard (5 pillars): Recommended for most campaigns - Extended (7 pillars): For complex products/audiences **4. Persona Depth** - Light: Basic persona-message mapping - Standard: Full persona profiles with message angles - Deep: Include persona journey mapping per phase **5. Moment Planning Scope** - Essential only: 3-5 key moments scripted - Comprehensive: All milestones with messaging - Crisis-inclusive: Add crisis communication templates **6. Message Library Size** - Starter: 20-30 components - Standard: 50-75 components - Extensive: 100+ components with variations """, validation_recommendations=""" **VALIDATION CHECKLIST:** **Strategic Alignment:** ☐ Pillar activation pattern supports phase objectives ☐ Persona messaging addresses actual pain points ☐ Platform adaptations respect platform culture ☐ Message emphasis matches campaign goals ☐ Key moments have appropriate messaging weight **Completeness:** ☐ All phases have pillar priorities assigned ☐ All personas have message angles defined ☐ All platforms have adaptation guides ☐ Critical moments have scripts prepared ☐ Message library covers main categories **Practical Usability:** ☐ Matrix can be referenced quickly during content creation ☐ Phase guides fit on one page ☐ Message library components are copy-paste ready ☐ Platform voice differences are clear ☐ Output block contains all downstream requirements **Consistency Check:** ☐ Brand voice maintained across all adaptations ☐ Pillar messages don't contradict each other ☐ Persona angles align with brand positioning ☐ CTAs match phase objectives ☐ Proof points are accurate and current **Testing Recommendations:** 1. **Pillar test:** Can you explain each pillar in 10 seconds? 2. **Persona test:** Would each persona recognize themselves? 3. **Platform test:** Does adapted content feel native? 4. **Moment test:** Read key moment scripts aloud—do they flow? 5. **Library test:** Create one post using only library components **Red Flags to Address:** 🚩 Pillars overlap significantly in meaning 🚩 Persona messages all sound the same 🚩 Platform adaptations are just length changes 🚩 Key moment scripts feel corporate/stilted 🚩 Message library has inconsistent quality **Quality Benchmarks:** - Matrix confidence rating: Target 80%+ overall - Phase guides: Actionable enough to create content immediately - Message library: 80% of components feel ready to use - Platform guides: Pass the "would this feel native?" test """)# =========================================================# END RECIPE-ID: RCP-004-002-009-MSG-MATRIX-v1.00a# =========================================================