lead-magnet-generator

Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.

---
name: lead-magnet-generator
description: Creates viral lead magnet posts that drive comments and DMs. Produces 2 versions - a quick punchy format and a detailed format with bullet points. Use when user needs social media posts to give away a lead magnet in exchange for engagement.
---

# Lead Magnet Generator

## Purpose
Generate 2 viral lead magnet posts that get your audience to comment a trigger word in exchange for a free resource, maximizing engagement and DM opt-ins.

---

## Execution Logic

**Check $ARGUMENTS first to determine execution mode:**

### If $ARGUMENTS is empty or not provided:
Respond with:
"lead-magnet-generator loaded, proceed with additional instructions"

Then wait for the user to provide their requirements in the next message.

### If $ARGUMENTS contains content:
Proceed immediately to Task Execution (skip the "loaded" message).

---

## Task Execution

When user requirements are available (either from initial $ARGUMENTS or follow-up message):

### 1. MANDATORY: Read Reference Files FIRST
**BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP**

Before doing ANYTHING else, you MUST use the Read tool to read ALL reference files:

```
Read: ./references/lead-magnet-patterns.md
Read: ../viral-hook-creator/references/hook-patterns.md
Read: ../viral-hook-creator/references/trigger_words.md
```

**What you will find:**
- **lead-magnet-patterns.md**: Lead magnet post structures, value framing techniques, and CTA patterns
- **hook-patterns.md**: 18 proven viral hook patterns with templates and psychology (from viral-hook-creator)
- **trigger_words.md**: Four categories of viral trigger words (from viral-hook-creator)

**DO NOT PROCEED** to Step 2 until you have read ALL three files and have the patterns loaded in context.

### 2. Check for Business Context
Check if `FOUNDER_CONTEXT.md` exists in the project root.
- **If it exists:** Read it and use the business context to personalize your output (industry terminology, audience, brand voice, authority metrics).
- **If it doesn't exist:** Proceed using defaults from the "Defaults & Assumptions" section.

### 3. Analyze Input
From the user's requirements, extract:
- **Lead magnet:** What are they giving away? (framework, template, checklist, course, etc.)
- **Credibility hook:** What effort/research backs it? (X hours studying, X months building, X years experience)
- **Inside contents:** What does the lead magnet contain? (for the detailed version)
- **Value anchor:** Price point to anchor value ($99, $199, etc.) or scarcity (will charge X in Y days)
- **Trigger word:** What word should people comment? (default: relevant keyword in CAPS)
- **Platform:** Twitter/X or LinkedIn

For any missing information, apply defaults from **Defaults & Assumptions** or ask the user.

### 4. Generate Lead Magnet Posts

**Step 4a: Generate Opening Hooks FIRST**
Using the hook patterns and trigger words from viral-hook-creator (read in Step 1), generate exactly 2 opening hook options:

1. Select 2 different patterns from hook-patterns.md that fit the lead magnet topic
2. Integrate 1-2 trigger words from trigger_words.md into each hook
3. Each hook should be 1-2 lines that create curiosity about the lead magnet

These hooks will serve as the opening lines for both post versions.

**Step 4b: Build Complete Posts**
Using the best hook from 4a, create exactly 2 versions:

**Version 1: Quick Format**
Structure:
```
[Opening hook from Step 4a]

[What you created from it]

[Value anchor - could charge $X / will charge $X soon]

Comment "[WORD]" and I'll send it to you for free (must be following)
```

**Version 2: Detailed Format**
Structure:
```
[Opening hook from Step 4a]

[What you built from it]

Inside you'll find:

→ [Benefit/content 1]
→ [Benefit/content 2]
→ [Benefit/content 3]
→ [Benefit/content 4]

Want the full [playbook/framework/guide]?

Comment "[WORD]" and I'll send it to you.

(Must be following)
```

**Platform Adaptation:**
- **Twitter/X:** Use the standard CTA endings abo