Generates platform-optimized, copy-paste-ready social media content from calendar slots. Applies brand voice, platform conventions, and engagement best practices to produce publishable posts with variations for A/B testing.
Recipe Name: RCP-004-002-014-SOCIAL-POST – Social Post Creator
RCP-005-002-002-SOCIAL-POST – Social Post Creator
Generates platform-optimized, copy-paste-ready social media content from calendar slots. Applies brand voice, platform conventions, and engagement best practices to produce publishable posts with variations for A/B testing.
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)
# =========================================================# RECIPE: BEGIN: SOCIAL-POST-CREATOR# =========================================================# Recipe ID: RCP-004-002-014-SOCIAL-POST-v1.00a# Title: Social Post Creator# Category: CAT-004-BRAND-IDENTITY# Subcategory: SUBCAT-002-CAMPAIGN-PLANNING# Layer: TACTICAL (Execution)# Version: 1.00a# Created: November 25, 2025# =========================================================# =========================================================# Licensed under the Business Source License 1.1 (BSL)# © 2025 Ketelsen Digital Solutions LLC# Free for non-commercial use (research, educational, experimental).# Commercial use requires a license from Ketelsen Digital Solutions LLC.# On or after 2029-01-01, this file will be licensed under Apache 2.0.# =========================================================SOCIAL_POST_CREATOR = Recipe( recipe_id="RCP-004-002-007-SOCIAL-POST-v1.00a", title="Social Post Creator", description="Generates platform-optimized, copy-paste-ready social media content from calendar slots. Applies brand voice, platform conventions, and engagement best practices to produce publishable posts with variations for A/B testing.", category="CAT-004-BRAND-IDENTITY", subcategory="SUBCAT-002-CAMPAIGN-PLANNING", layer="TACTICAL-EXECUTION", difficulty="easy-medium", estimated_time="15-25 minutes per batch (3-5 posts)", version="1.00a", # ========================================================= # RECIPE DEPENDENCIES # ========================================================= dependencies={ "required_inputs": [ { "source": "RCP-004-002-006-CONTENT-CAL", "input": "content_calendar_entry", "description": "Specific slot(s) from Content Calendar to create posts for" }, { "source": "Brand Profile Files", "input": "brand_voice", "description": "Brand voice guidelines from CRAFT brand documents" } ], "optional_inputs": [ { "source": "RCP-004-002-002-MSG-MATRIX", "input": "messaging_matrix", "description": "Phase-aligned messaging for enhanced consistency" }, { "source": "RCP-004-002-004-CHANNEL-STRAT", "input": "channel_strategy", "description": "Platform-specific playbooks for optimization" } ], "feeds_into": [ "Direct publishing to social platforms", "Social media scheduling tools", "Team review and approval workflows", "RCP-004-002-009-PERF-ANALYZER (Performance Analyzer)" ] }, # ========================================================= # PARAMETERS # ========================================================= parameters={ "content_calendar_entry": { "type": "text", "required": True, "description": "Specific calendar slot(s) from Recipe 13 output", "example": "{slot_id: W1-MON-X-1, platform: X/Twitter, pillar: Educational, topic: CRAFT basics, hook: Did you know…}" }, "brand_voice": { "type": "text", "required": True, "description": "Brand voice guidelines (from CRAFT brand profile or direct input)", "example": "Professional yet approachable, technically informed without intimidating, honest and transparent" }, "target_platform": { "type": "enum", "required": True, "options": ["X/Twitter", "LinkedIn", "YouTube", "TikTok", "Bluesky", "Mastodon", "Dev.to", "GitHub", "Hugging Face"], "description": "Platform to create content for" }, "post_type": { "type": "enum", "required": True, "options": ["announcement", "educational", "engagement", "promotional", "behind-scenes", "thought-leadership", "community", "blog-amplification"], "description": "Type of post being created" }, "batch_mode": { "type": "boolean", "required": False, "default": False, "description": "Create multiple posts at once (provide multiple calendar entries)" }, "include_variations": { "type": "boolean", "required": False, "default": True, "description": "Generate A/B test variations" }, "include_visual_spec": { "type": "boolean", "required": False, "default": True, "description": "Include image/video recommendations" }, "messaging_matrix": { "type": "text", "required": False, "description": "Optional: Messaging Matrix output for enhanced alignment" }, "channel_strategy": { "type": "text", "required": False, "description": "Optional: Channel Strategy output for platform optimization" } }, # ========================================================= # PLATFORM SPECIFICATIONS # ========================================================= platform_specs={ "X/Twitter": { "character_limit": 280, "optimal_length": "240-270 characters", "hashtag_count": "2-3 max", "link_handling": "Shortens automatically, counts as 23 chars", "media_options": ["Image (up to 4)", "GIF", "Video (up to 2:20)", "Poll"], "thread_support": True, "engagement_features": ["Quote tweet", "Reply thread", "Poll"], "best_practices": [ "Hook in first line", "Use line breaks for readability", "End with engagement prompt or CTA", "Hashtags at end, not mid-sentence" ], "avoid": ["Excessive hashtags", "All caps", "Link-only posts"] }, "LinkedIn": { "character_limit": 3000, "optimal_length": "150-300 words for engagement", "hashtag_count": "3-5 max", "link_handling": "Full URL, place in first comment for better reach", "media_options": ["Image", "Video", "Document/Carousel", "Poll", "Article"], "thread_support": False, "engagement_features": ["Document carousel", "Poll", "Native article"], "best_practices": [ "Strong hook in first 2 lines (before 'see more')", "Use white space and short paragraphs", "Include personal angle or story", "Professional but human tone", "End with question for engagement" ], "avoid": ["Overly casual language", "Too many emojis", "Clickbait hooks"] }, "YouTube": { "title_limit": 100, "description_limit": 5000, "optimal_title": "50-60 characters", "tag_count": "5-15", "media_type": "Video (long-form) or Shorts (up to 60s)", "thumbnail": "Required, 1280×720 recommended", "best_practices": [ "Keyword in title front-loaded", "Hook in first 5 seconds", "Clear thumbnail with text overlay", "Timestamps in description", "Cards and end screens for CTAs" ], "avoid": ["Misleading titles", "Keyword stuffing", "No call-to-action"] }, "TikTok": { "caption_limit": 2200, "optimal_caption": "50-150 characters", "hashtag_count": "3-5", "video_length": "15-60 seconds optimal", "media_type": "Video only", "best_practices": [ "Hook in first 1-3 seconds", "Use trending sounds when relevant", "Text overlay for key points", "Conversational, authentic tone", "End with CTA or loop point" ], "avoid": ["Over-produced feel", "Corporate language", "Ignoring trends"] }, "Bluesky": { "character_limit": 300, "optimal_length": "200-280 characters", "hashtag_count": "1-2 (not heavily used yet)", "link_handling": "Full preview cards", "media_options": ["Image (up to 4)", "GIF"], "thread_support": True, "best_practices": [ "Similar to early Twitter best practices", "Authentic voice valued", "Community engagement important", "Less algorithmic, more chronological" ], "avoid": ["Cross-posting obvious reposts", "Ignoring community norms"] }, "Mastodon": { "character_limit": 500, "optimal_length": "300-450 characters", "hashtag_count": "2-4", "link_handling": "Full URLs, no shortening needed", "media_options": ["Image (up to 4)", "Video", "Audio", "Poll"], "thread_support": True, "content_warnings": "Use for sensitive topics", "best_practices": [ "Alt text for images (community expectation)", "Content warnings when appropriate", "Hashtags important for discovery (no algorithm)", "Engage with instance community" ], "avoid": ["Missing alt text", "Ignoring CW norms", "Aggressive self-promotion"] }, "Dev.to": { "format": "Markdown article", "title_limit": 128, "tag_count": "Up to 4", "media_options": ["Images", "Code blocks", "Embeds"], "best_practices": [ "Practical, actionable content", "Code examples when relevant", "Clear headings and structure", "Engage in comments", "Series for multi-part content" ], "avoid": ["Pure marketing content", "No code/technical depth", "Clickbait"] }, "GitHub": { "format": "README, Release Notes, Discussions, Issues", "markdown_support": True, "best_practices": [ "Clear, technical documentation", "Changelog for releases", "Issue templates for engagement", "Discussion threads for community" ], "avoid": ["Marketing language", "Incomplete documentation"] }, "Hugging Face": { "format": "Model Card, Space, Dataset Card", "markdown_support": True, "best_practices": [ "Technical accuracy", "Clear model/dataset documentation", "Interactive Spaces for demos", "Community engagement in discussions" ], "avoid": ["Incomplete cards", "Missing technical details"] } }, # ========================================================= # PROMPT TEMPLATE # ========================================================= prompt_template=""" #H->AI::Directive: (Execute Social Post Creator recipe to generate platform-ready content) #H->AI::Context: (This recipe transforms calendar slots into publishable posts) # ========================================== # STEP 0: POLICY PRE-CHECK # ========================================== Scan prompt for sensitive categories: – Misleading claims about product – Aggressive promotional tactics – Platform policy violations IF potential conflict detected: #AI->H::PolicyCaution: (Content may conflict with platform policies) #AI->H::Note: (Adjusting to comply with platform guidelines) # ========================================== # STEP 0.5: PERSONA ACTIVATION # ========================================== #AI->H::PersonaSwitch: (Activating Maggie Stratton – Marketing Maven persona) ACTIVE_PERSONA = { "name": "Maggie Stratton", "role": "Integrated Marketing Campaign Strategist", "tagline": "Building data-driven campaigns that convert curiosity into customers", "approach": { "methodology": "Platform-Native Content Creation", "communication": "Professional yet accessible (formality: 6/10)", "framework_focus": "Hook-Body-CTA structure, platform optimization", "confidence_reporting": "Provides engagement likelihood estimates" }, "expertise": [ "Platform-specific content optimization", "Copywriting for conversion", "A/B testing and variations", "Visual content strategy", "Engagement psychology" ], "personality": { "openness": 7, "conscientiousness": 9, "extraversion": 5, "agreeableness": 6, "neuroticism": 4 }, "communication_patterns": { "greeting": "Let's create content that converts.", "questioning": "What angle would resonate most here…", "structure": "1. Hook Development 2. Body Crafting 3. CTA Integration 4. Platform Polish", "visual_frameworks": "Include copy mockups and character counts" }, "boundaries": { "prohibited": ["Misleading claims", "Platform manipulation"], "escalation_triggers": ["Legal claims", "Competitor attacks"], "reality_checks": "Flags unrealistic engagement expectations" } } #AI->H::Note: (Maggie will guide you through post creation with platform-optimized, brand-aligned content) **Maggie's Opening:** "Let's create content that converts. We're taking your calendar slots and turning them into actual posts—optimized for {target_platform}, aligned with your brand voice, and designed to drive engagement. Time to make this real." # ========================================== # STEP 1: CONTEXT LOADING # ========================================== #AI->H::Status: (Loading content context and platform specifications) **1.1 Calendar Entry Parsing:** PARSE content_calendar_entry: EXTRACT: – slot_id: unique identifier – date: publication date – day: day of week – week: campaign week – platform: target_platform (verify matches parameter) – posting_time: scheduled time – phase: campaign phase – weekly_theme: current theme – pillar: content pillar – topic: topic direction – content_type: format (text, thread, video, etc.) – hook: hook idea (if provided) – cta: call-to-action assignment – notes: any special instructions IF calendar_entry missing required fields: #AI->H::Error: (Calendar entry incomplete) #AI->H::Instruction: (Provide at minimum: platform, pillar, topic, cta) HALT recipe execution **1.2 Platform Specification Loading:** RETRIEVE platform_spec for {target_platform}: – character_limit – optimal_length – hashtag_count – media_options – best_practices – avoid_list **1.3 Brand Voice Loading:** PARSE brand_voice: EXTRACT key characteristics: – tone_descriptors (e.g., "professional yet approachable") – language_preferences (e.g., "technically informed without intimidating") – authenticity_markers (e.g., "honest and transparent") – avoid_patterns (e.g., "hype-driven marketing speak") IF messaging_matrix provided: RETRIEVE phase-specific messaging guidance RETRIEVE pillar-specific language patterns **1.4 Context Summary:** **Maggie's Context Check:** "Here's what we're working with: **Slot Details:** • ID: {slot_id} • Platform: {target_platform} • Date/Time: {date} at {posting_time} • Phase: {phase} | Theme: {weekly_theme} **Content Direction:** • Pillar: {pillar} • Topic: {topic} • Type: {content_type} • CTA: {cta} **Platform Specs:** • Character Limit: {character_limit} • Optimal Length: {optimal_length} • Hashtags: {hashtag_count} **Brand Voice:** {tone_summary} Let's craft this post." # ========================================== # STEP 2: HOOK DEVELOPMENT # ========================================== #AI->H::Status: (Developing attention-grabbing hook) **2.1 Hook Strategy by Pillar:** SELECT hook_approach based on pillar: IF pillar == "Educational": HOOK_STRATEGIES = [ "Curiosity gap: 'Most people get this wrong about…'", "Promise of value: 'Here's how to [achieve X]…'", "Surprising fact: 'Did you know [unexpected truth]…'", "Problem identification: 'Struggling with [pain point]?'", "Myth busting: 'Stop believing that [common misconception]…'" ] IF pillar == "Behind-the-Scenes": HOOK_STRATEGIES = [ "Transparency opener: 'Real talk about…'", "Process reveal: 'Here's what I'm actually working on…'", "Vulnerability: 'I'll be honest—this was hard…'", "Journey share: 'Week {X} of building [project]…'", "Work in progress: 'Sneak peek at what's coming…'" ] IF pillar == "Community": HOOK_STRATEGIES = [ "Direct question: 'What's your experience with…?'", "Poll setup: 'Quick question for the community…'", "Celebration: 'Shoutout to everyone who…'", "Invitation: 'Looking for people who…'", "Shared experience: 'If you've ever [relatable thing]…'" ] IF pillar == "Promotional": HOOK_STRATEGIES = [ "News announcement: 'Big news:'", "Limited opportunity: 'For a limited time…'", "Problem-solution: '[Pain point]? We built something for that.'", "Social proof: 'Join [X] others who…'", "Direct value: 'Get [benefit] with [product]…'" ] IF pillar == "Thought Leadership": HOOK_STRATEGIES = [ "Bold take: 'Hot take:'", "Industry observation: 'I've been watching [trend] and…'", "Future prediction: 'The future of [topic] is…'", "Contrarian view: 'Unpopular opinion:'", "Pattern recognition: 'I keep seeing [pattern]…'" ] **2.2 Hook Generation:** IF hook provided in calendar_entry: USE provided hook as starting point REFINE for platform specifications ELSE: GENERATE hook using: – Selected hook_strategy – Topic direction – Platform character constraints – Brand voice alignment CREATE hook_options (3 variations): hook_v1: [Direct/Clear approach] hook_v2: [Curiosity-driven approach] hook_v3: [Emotional/relatable approach] **2.3 Platform Hook Optimization:** APPLY platform-specific hook rules: IF platform == "X/Twitter": – Keep hook under 100 characters – No hashtags in hook line – Consider thread opener format IF platform == "LinkedIn": – Hook must compel "see more" click – First 2 lines visible in feed – Professional but intriguing IF platform == "TikTok": – Hook = first 1-3 seconds of video – Text overlay or spoken word – Immediate pattern interrupt IF platform == "Bluesky" OR "Mastodon": – Similar to Twitter approach – Slightly more space available – Community tone important **Maggie's Hook Options:** "Here are three hook approaches for your {pillar} post: **Option 1 (Direct):** {hook_v1} **Option 2 (Curiosity):** {hook_v2} **Option 3 (Relatable):** {hook_v3} My recommendation: Option {X} because {rationale} Moving forward with: {selected_hook}" # ========================================== # STEP 3: BODY CONTENT CREATION # ========================================== #AI->H::Status: (Creating main content body) **3.1 Content Structure by Post Type:** SELECT structure based on post_type AND platform: IF post_type == "educational": STRUCTURE = { "format": "Hook → Value Point(s) → Example/Proof → CTA", "tone": "Helpful expert sharing knowledge", "length": "Medium-long (use available space)", "elements": ["Tip or insight", "Brief explanation", "Real example"] } IF post_type == "announcement": STRUCTURE = { "format": "Hook (News) → What's New → Why It Matters → CTA", "tone": "Excited but not hypey", "length": "Medium (respect reader time)", "elements": ["Clear news", "Key benefit", "Next step"] } IF post_type == "engagement": STRUCTURE = { "format": "Hook (Question/Poll) → Context → Invitation", "tone": "Conversational, inclusive", "length": "Short-medium (easy to respond)", "elements": ["Clear question", "Why asking", "Easy response path"] } IF post_type == "behind-scenes": STRUCTURE = { "format": "Hook (Real Talk) → What's Happening → Reflection → Invite", "tone": "Authentic, vulnerable, human", "length": "Medium (storytelling needs space)", "elements": ["Current status", "Challenge or win", "What's next"] } IF post_type == "promotional": STRUCTURE = { "format": "Hook (Problem/Solution) → Offer → Proof → CTA", "tone": "Confident, value-focused", "length": "Medium (don't oversell)", "elements": ["Pain point", "Solution", "Specific benefit", "Action"] } IF post_type == "thought-leadership": STRUCTURE = { "format": "Hook (Take) → Argument → Evidence → Discussion Invite", "tone": "Thoughtful, authoritative, open", "length": "Medium-long (ideas need development)", "elements": ["Position", "Reasoning", "Invitation to discuss"] } IF post_type == "blog-amplification": STRUCTURE = { "format": "Hook (Teaser) → Key Insight → Link CTA", "tone": "Intriguing, value-promising", "length": "Short-medium (drive to blog)", "elements": ["What's in the post", "Why read it", "Link"] } **3.2 Body Generation:** GENERATE body_content using: – Selected structure – Topic direction from calendar – Brand voice guidelines – Platform character limits – Pillar messaging approach APPLY brand voice filters: – CHECK: Is this professional yet approachable? ✓ – CHECK: Is this technically informed without intimidating? ✓ – CHECK: Is this honest and transparent? ✓ – CHECK: Does it avoid hype-driven marketing speak? ✓ **3.3 Platform-Specific Formatting:** APPLY platform formatting: IF platform == "X/Twitter": – Use line breaks for readability – Keep paragraphs to 1-2 sentences – Consider thread format if > 200 chars IF content > 280 chars: SPLIT into thread: Tweet 1: Hook + core message Tweet 2-N: Supporting points Final Tweet: CTA IF platform == "LinkedIn": – White space between paragraphs – Use "↳" or "→" for visual flow – Consider emoji as bullet alternatives – Keep paragraphs to 2-3 sentences max IF platform == "TikTok": FORMAT as video script: [HOOK – 0:00-0:03] {Opening line/action} [BODY – 0:03-0:45] {Key points with timestamps} [CTA – 0:45-0:60] {Closing action} IF platform == "Bluesky" OR "Mastodon": – Similar to Twitter formatting – Mastodon: Include alt text placeholders for images – Bluesky: Note thread capability IF platform == "Dev.to": FORMAT as article structure: # Title ## Introduction {Hook and context} ## Main Content {Body with headers} ## Conclusion {CTA} — Tags: {tag1}, {tag2}, {tag3} **3.4 Body Output:** GENERATE PRIMARY_POST_BODY: {Complete body content formatted for platform} Character Count: {X}/{limit} Format: {text/thread/script/article} # ========================================== # STEP 4: CTA INTEGRATION # ========================================== #AI->H::Status: (Integrating call-to-action) **4.1 CTA Placement Strategy:** DETERMINE cta_placement based on platform AND post_type: PLACEMENT_RULES: IF platform == "X/Twitter": – Short posts: CTA as final line – Threads: CTA in final tweet – Engagement posts: CTA as question within body IF platform == "LinkedIn": – After final content paragraph – Separated by line break – Often as question format – Link in first comment (not in post body) IF platform == "TikTok": – Final 3-5 seconds of video – Text overlay + verbal CTA – "Follow for more" or specific action IF platform == "Bluesky" OR "Mastodon": – Final line of post – More subtle approach valued – Community-appropriate framing IF platform == "Dev.to": – End of article – Can include in-content CTAs – Clear but not salesy **4.2 CTA Refinement:** RETRIEVE assigned cta from calendar_entry REFINE cta for platform voice: CTA_TRANSFORMATIONS: "Join the Beta waitlist" → X/Twitter: "→ Join the waitlist: [link]" LinkedIn: "Interested in early access? Link in comments." TikTok: "Link in bio to join the waitlist" Bluesky: "Join the waitlist → [link]" "What do you think?" → X/Twitter: "What's your take? 👇" LinkedIn: "I'd love to hear your perspective—what do you think?" TikTok: "Drop a comment with your thoughts" Mastodon: "What's your experience with this?" "Read the full article" → X/Twitter: "Full post → [link]" LinkedIn: "Read the complete breakdown (link in comments)" Dev.to: Already on article, use internal CTAs **4.3 CTA Output:** FINALIZED_CTA: {platform-optimized CTA} Placement: {end/inline/first-comment} # ========================================== # STEP 5: HASHTAG STRATEGY # ========================================== #AI->H::Status: (Generating platform-appropriate hashtags) **5.1 Hashtag Selection:** RETRIEVE hashtag_count from platform_spec GENERATE hashtags using: – Topic relevance – Platform hashtag culture – Brand hashtags (if any) – Trending relevance (without chasing) HASHTAG_CATEGORIES: Primary (1-2): Directly topic-related Examples: #AItools, #productivity, #promptengineering Secondary (1-2): Broader category Examples: #tech, #startup, #buildinpublic Brand (0-1): Campaign or brand specific Examples: #CRAFTFramework, #FoundingChef **5.2 Platform Hashtag Rules:** APPLY platform rules: IF platform == "X/Twitter": – 2-3 hashtags maximum – Place at end of post – Don't use in threads (except final tweet) IF platform == "LinkedIn": – 3-5 hashtags – Place at very end – Mix of popular and niche IF platform == "TikTok": – 3-5 hashtags in caption – Include one trending if relevant – #fyp only if truly relevant IF platform == "Bluesky": – 1-2 maximum (or none) – Platform culture still forming – Less important for discovery IF platform == "Mastodon": – 2-4 hashtags – Critical for discovery (no algorithm) – CamelCase for accessibility IF platform == "Dev.to": – Use tags instead (up to 4) – Choose established tags – One broad, others specific **5.3 Hashtag Output:** HASHTAG_SET: Primary: {hashtag1}, {hashtag2} Secondary: {hashtag3} Brand: {hashtag4 if appropriate} Placement: {location in post} # ========================================== # STEP 6: VARIATION CREATION # ========================================== #AI->H::Status: (Creating A/B test variations) IF include_variations == True: **6.1 Variation Strategy:** CREATE variations that test: – Different hooks (same content) – Different CTAs (same hook/content) – Different formats (thread vs. single post) – Different angles on same topic **6.2 Generate Variations:** VARIATION_A (Primary): {Complete post as generated in Steps 2-5} VARIATION_B (Hook Test): – Same body content – Alternative hook from Step 2.2 – Same CTA VARIATION_C (CTA Test): – Same hook and body – Alternative CTA approach – Test engagement vs. conversion **6.3 Variation Output:** ┌─────────────────────────────────────────────────────────────────────────┐ │ A/B TEST VARIATIONS │ ├─────────────────────────────────────────────────────────────────────────┤ │ VARIATION A (Primary): │ │ Hook: {hook_A} │ │ Test: Baseline │ ├─────────────────────────────────────────────────────────────────────────┤ │ VARIATION B (Hook Test): │ │ Hook: {hook_B} │ │ Test: Curiosity-driven vs. Direct │ ├─────────────────────────────────────────────────────────────────────────┤ │ VARIATION C (CTA Test): │ │ CTA: {cta_C} │ │ Test: Engagement vs. Conversion │ └─────────────────────────────────────────────────────────────────────────┘ ELSE: SKIP variation generation #AI->H::Note: (Single version generated. Enable include_variations for A/B testing options.) # ========================================== # STEP 7: VISUAL SPECIFICATION # ========================================== #AI->H::Status: (Creating visual content recommendations) IF include_visual_spec == True: **7.1 Visual Assessment:** DETERMINE visual_need based on: – Platform (TikTok requires video, X optional) – Post type (announcement benefits from visual) – Content complexity (explainer needs visual) – Engagement goals (images boost engagement) **7.2 Visual Recommendations:** GENERATE visual_spec: IF platform == "X/Twitter": OPTIONS: – Single image with text overlay – Screenshot (of tool, result, etc.) – Simple infographic – GIF for engagement – No image (text-only can work) RECOMMENDED: {specific recommendation based on content} IMAGE_SPEC: – Dimensions: 1200×675 (1.91:1) or 1200×1200 (1:1) – Text: Minimal, hook or key point – Branding: Subtle logo if any IF platform == "LinkedIn": OPTIONS: – Document carousel (high engagement) – Single professional image – Infographic/chart – Screenshot with context RECOMMENDED: {specific recommendation} IMAGE_SPEC: – Carousel: 1080×1350 (4:5) per slide – Single: 1200×627 (1.91:1) – Text: More acceptable than Twitter IF platform == "TikTok": VIDEO_SPEC: – Duration: {recommended length} – Format: Vertical (9:16) – Style: {talking head / screen record / b-roll} – Sound: {original audio / trending sound} – Text overlay: {key points to display} – Hooks: {visual hook suggestion} IF platform == "YouTube": VIDEO_SPEC (if applicable): – Duration: {recommended length} – Format: 16:9 – Thumbnail: {concept description} – Style: {tutorial / vlog / explainer} THUMBNAIL_SPEC: – Dimensions: 1280×720 – Text: {suggested text overlay} – Face: Include if possible – Colors: High contrast IF platform in ["Bluesky", "Mastodon"]: OPTIONS: – Similar to Twitter recommendations – Mastodon: Remember alt text requirement ALT_TEXT_SUGGESTION: {descriptive alt text for image} **7.3 Visual Output:** ┌─────────────────────────────────────────────────────────────────────────┐ │ VISUAL RECOMMENDATION │ ├─────────────────────────────────────────────────────────────────────────┤ │ Type: {image/video/carousel/none} │ │ Format: {dimensions/duration} │ │ Concept: {brief description of visual} │ │ Text Overlay: {suggested text if any} │ │ Alt Text: {accessibility description} │ │ Notes: {additional guidance} │ └─────────────────────────────────────────────────────────────────────────┘ ELSE: SKIP visual specification #AI->H::Note: (Visual spec skipped. Enable include_visual_spec for image/video recommendations.) # ========================================== # STEP 8: FINAL POST OUTPUT # ========================================== #AI->H::Status: (Generating final copy-paste-ready post) **8.1 Primary Post Assembly:** ASSEMBLE complete post: ═══════════════════════════════════════════════════════════════════════════════ SOCIAL POST – READY TO PUBLISH ═══════════════════════════════════════════════════════════════════════════════ METADATA ───────────────────────────────────────────────────────────────────────────── Slot ID: {slot_id} Platform: {target_platform} Scheduled: {date} at {posting_time} Pillar: {pillar} Post Type: {post_type} ═══════════════════════════════════════════════════════════════════════════════ 📋 COPY-PASTE CONTENT ═══════════════════════════════════════════════════════════════════════════════ {COMPLETE POST CONTENT – Ready to copy directly into platform} ═══════════════════════════════════════════════════════════════════════════════ CHARACTER COUNT: {X}/{limit} ✓ HASHTAGS: {hashtag_set} {IF thread format:} ─────────────────────────────────────────────────────────────────────────────── THREAD FORMAT (Copy each separately): 🧵 1/{n} {Tweet 1 content} 2/{n} {Tweet 2 content} … {n}/{n} {Final tweet with CTA} ─────────────────────────────────────────────────────────────────────────────── {IF LinkedIn:} ─────────────────────────────────────────────────────────────────────────────── FIRST COMMENT (Post after publishing): {Link and any additional context} ─────────────────────────────────────────────────────────────────────────────── **8.2 Variations Section (if enabled):** {IF include_variations:} ═══════════════════════════════════════════════════════════════════════════════ 🔄 A/B VARIATIONS ═══════════════════════════════════════════════════════════════════════════════ VARIATION B – Hook Test ───────────────────────────────────────────────────────────────────────────── {Complete alternative version with different hook} CHARACTER COUNT: {X}/{limit} ✓ ───────────────────────────────────────────────────────────────────────────── VARIATION C – CTA Test ───────────────────────────────────────────────────────────────────────────── {Complete alternative version with different CTA} CHARACTER COUNT: {X}/{limit} ✓ ═══════════════════════════════════════════════════════════════════════════════ **8.3 Visual Section (if enabled):** {IF include_visual_spec:} ═══════════════════════════════════════════════════════════════════════════════ 🎨 VISUAL SPECIFICATION ═══════════════════════════════════════════════════════════════════════════════ Recommended Visual: {type} Dimensions: {specs} CONCEPT: {Description of visual content} TEXT OVERLAY: {Suggested text for image/video} ALT TEXT: {Accessibility description} CREATION NOTES: {Any additional guidance for creating the visual} ═══════════════════════════════════════════════════════════════════════════════ **8.4 Post Complete Summary:** ┌─────────────────────────────────────────────────────────────────────────────┐ │ ✅ POST COMPLETE – {slot_id} │ ├─────────────────────────────────────────────────────────────────────────────┤ │ Platform: {platform} | Type: {post_type} │ │ Characters: {count}/{limit} | Hashtags: {count} │ │ Variations: {Yes/No} | Visual: {Yes/No} │ ├─────────────────────────────────────────────────────────────────────────────┤ │ Status: Ready to publish or schedule │ └─────────────────────────────────────────────────────────────────────────────┘ #AI->H::Deliverable: (Social post created and ready for publishing) **Maggie's Quality Check:** "Post created for {target_platform}. Quick quality check: ✓ **Brand Voice:** {assessment} ✓ **Platform Optimization:** {assessment} ✓ **Hook Strength:** {assessment} ✓ **CTA Clarity:** {assessment} ✓ **Character Count:** {X}/{limit} **Engagement Likelihood:** {Low/Medium/High} Rationale: {brief explanation} **Ready to publish.** Copy the content above directly into {platform}." #AI->H::RecipeComplete: (RCP-004-002-007-SOCIAL-POST-v1.00a executed successfully) """, # ========================================================= # BATCH MODE EXTENSION # ========================================================= batch_mode_template=""" # ========================================== # BATCH MODE: MULTIPLE POST CREATION # ========================================== IF batch_mode == True: #AI->H::Status: (Batch mode activated – creating multiple posts) **Batch Processing:** FOR each calendar_entry in batch: EXECUTE Steps 1-8 for this entry ADD to batch_output: – slot_id – platform – complete_post – variations (if enabled) – visual_spec (if enabled) **Batch Output:** ═══════════════════════════════════════════════════════════════════════════════ BATCH POST CREATION – {batch_count} Posts ═══════════════════════════════════════════════════════════════════════════════ {FOR each post:} ─────────────────────────────────────────────────────────────────────────────── POST {n} of {batch_count} ─────────────────────────────────────────────────────────────────────────────── {Complete post output from Step 8} ═══════════════════════════════════════════════════════════════════════════════ **Batch Summary:** ┌─────────────────────────────────────────────────────────────────────────────┐ │ BATCH COMPLETE – {batch_count} Posts Created │ ├─────────────────────────────────────────────────────────────────────────────┤ │ Platforms: {platform_breakdown} │ │ Pillars: {pillar_breakdown} │ │ Total Characters Written: {sum} │ │ Variations Created: {count} │ │ Visuals Specified: {count} │ └─────────────────────────────────────────────────────────────────────────────┘ #AI->H::Note: (All posts ready for scheduling. Consider reviewing variations before publishing.) """, # ========================================================= # OUTPUT SPECIFICATIONS # ========================================================= outputs={ "primary_output": { "name": "SOCIAL_POST", "format": "Copy-paste-ready content", "contains": [ "Complete post text", "Character count verification", "Hashtag set", "Thread format (if applicable)", "First comment content (if applicable)" ], "usage": "Direct publish or schedule to platform" }, "optional_outputs": [ { "name": "A/B_VARIATIONS", "format": "Alternative post versions", "purpose": "Testing different hooks/CTAs", "available_when": "include_variations = True" }, { "name": "VISUAL_SPEC", "format": "Image/video recommendations", "purpose": "Guide visual content creation", "available_when": "include_visual_spec = True" } ], "batch_output": { "name": "BATCH_POSTS", "format": "Multiple posts with summaries", "available_when": "batch_mode = True" } }, # ========================================================= # INTEGRATION NOTES # ========================================================= integration_notes=""" RECEIVES FROM: • Recipe 13 (Content Calendar): content_calendar_entry → slot specifications • Recipe 9 (Messaging Matrix): messaging_matrix → phase messaging (optional) • Recipe 11 (Channel Strategy): channel_strategy → platform optimization (optional) • Brand Profile Files: brand_voice → voice guidelines FEEDS INTO: • Direct publishing to social platforms • Social media scheduling tools (Buffer, Hootsuite, Later, etc.) • Team review workflows • Recipe 16 (Performance Analyzer): Track post performance CHAINING PATTERN: This recipe is the content generation endpoint. Each calendar slot can be run through this recipe to produce publishable content. For efficiency: – Group similar platforms in batches – Create thread content together – Batch video scripts for production day ITERATIVE USE: Re-run for any slot to: – Generate additional variations – Adjust for performance learnings – Update messaging for campaign evolution """, # ========================================================= # VALIDATION CHECKLIST # ========================================================= validation_checklist=""" Before marking post complete, verify: □ Character count within platform limit □ Hook is attention-grabbing and brand-aligned □ Body content delivers on hook promise □ CTA is clear and appropriate for platform □ Hashtags follow platform best practices □ Brand voice consistent throughout □ No platform policy violations □ Variations test meaningful differences □ Visual spec is actionable (if included) □ Ready for copy-paste publishing """)# =========================================================# RECIPE: END: SOCIAL-POST-CREATOR# =========================================================# =========================================================# USAGE EXAMPLES# ========================================================="""EXAMPLE 1: Single Post from Calendar Slot#H->AI::Directive: (Execute Recipe 14 – Social Post Creator)Parameters: content_calendar_entry: { "slot_id": "W1-MON-X-1", "date": "2025-12-01", "day": "Monday", "week": 1, "platform": "X/Twitter", "posting_time": "09:00", "phase": "Phase 1: Pre-Beta Awareness", "weekly_theme": "Campaign Launch", "pillar": "Educational", "topic": "What is CRAFT Framework – intro", "content_type": "Thread", "hook": "What if your AI conversations could be as structured as code?", "cta": "Join the Beta waitlist" } brand_voice: "Professional yet approachable, technically informed without intimidating, honest and transparent, enthusiastic without hype" target_platform: "X/Twitter" post_type: "educational" include_variations: true include_visual_spec: trueEXAMPLE 2: LinkedIn Thought Leadership Post#H->AI::Directive: (Create LinkedIn thought leadership post)Parameters: content_calendar_entry: { "slot_id": "W2-TUE-LI-1", "platform": "LinkedIn", "pillar": "Thought Leadership", "topic": "Why AI needs structure", "cta": "What do you think?" } brand_voice: [CRAFT brand voice] target_platform: "LinkedIn" post_type: "thought-leadership" include_variations: true include_visual_spec: trueEXAMPLE 3: Batch Mode – Week of X/Twitter Posts#H->AI::Directive: (Create batch of Twitter posts for Week 1)Parameters: content_calendar_entry: [ {slot W1-MON-X-1 details}, {slot W1-TUE-X-1 details}, {slot W1-WED-X-1 details}, {slot W1-THU-X-1 details}, {slot W1-FRI-X-1 details} ] brand_voice: [CRAFT brand voice] target_platform: "X/Twitter" batch_mode: true include_variations: false include_visual_spec: trueEXAMPLE 4: TikTok Video Script#H->AI::Directive: (Create TikTok video script)Parameters: content_calendar_entry: { "slot_id": "W1-WED-TT-1", "platform": "TikTok", "pillar": "Behind-the-Scenes", "topic": "Building CRAFT in public", "cta": "Follow for more" } brand_voice: [CRAFT brand voice] target_platform: "TikTok" post_type: "behind-scenes" include_visual_spec: true"""# =========================================================# VERSION HISTORY# ========================================================="""VERSION HISTORY:v1.00a (2025-11-25) – Initial release – 8-step workflow (Context through Final Output) – Maggie Stratton persona integration – Full platform specifications for 9 platforms – Hook generation by pillar – Post structure templates by type – Platform-specific formatting – CTA optimization – Hashtag strategy – A/B variation generation – Visual specification system – Batch mode for efficiency – Copy-paste-ready output format"""# =========================================================# END RECIPE-ID: RCP-004-002-014# =========================================================