linkedin-writer

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: linkedin-writer
description: Creates viral LinkedIn posts using proven formats, post templates, and voice matching. Use when user needs engaging, high-performing posts for LinkedIn.
---

# LinkedIn Writer

## Purpose
Generate 2 viral LinkedIn posts in different proven formats, matched to the founder's voice, using battle-tested templates and patterns that drive engagement on LinkedIn.

---

## Execution Logic

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

### If $ARGUMENTS is empty or not provided:
Respond with:
"linkedin-writer loaded, proceed with your topic or idea"

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. This is non-negotiable:

```
Read: ./references/linkedin-formats.md
Read: ./references/linkedin-posts.md
```

**What you will find:**
- **linkedin-formats.md**: 7 proven LinkedIn post formats with structure templates, psychology, rules, and when-to-use matching logic
- **linkedin-posts.md**: 8+ proven viral LinkedIn posts organized by format type — the example and voice library

**DO NOT PROCEED** to Step 2 until you have read all files and have their content 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 output (industry terminology, audience pain points, brand voice, company name, products, achievements).
- **If it doesn't exist:** Proceed using defaults from "Defaults & Assumptions."

### 3. Analyze Input & Auto-Select Formats
From the user's requirements, extract:
- **Topic/idea** — What they want to post about
- **Goal** — What they want the post to achieve (engagement, authority, leads, thought leadership)
- **Any specific format preference** — If they mentioned a format type

**Format Auto-Selection Logic:**

If the user specified a format → use that format for one post, auto-select the best complementary format for the second.

If the user did NOT specify a format, auto-select 2 different formats based on the topic:

| If the topic involves... | Best format match |
|---|---|
| Multiple tips, lessons, mistakes, or advice points | **Lessons Learned** |
| A complete process, roadmap, or "how to achieve X" | **Actionable Blueprint** |
| A personal experience, failure, setback, or pivotal moment | **Personal Story** |
| Explaining one specific technique, hack, or strategy with proof | **Strategy Breakdown** |
| Analyzing a specific company, product, or brand | **Case Study** |
| A strong opinion, industry trend, prediction, or contrarian view | **Industry Hot Take** |
| A small but impactful tip or optimization | **Quick Hack** |

**Always select 2 DIFFERENT formats.** Choose the primary format based on the strongest topic match, then select a complementary second format that gives the user a different angle on the same topic.

### 4. Generate 2 Viral LinkedIn Posts
Using the formats and posts you loaded in Steps 1-3:

1. **Study the example posts** in linkedin-posts.md for your selected formats — internalize the rhythm, structure, hook style, and length
2. **Extract the voice DNA** from the reference posts — match the writing style:
   - Conversational and direct, like talking to a peer
   - Short paragraphs (1-3 sentences each)
   - Heavy line breaks for readability
   - Mixes professional insight with personality
   - Uses specific numbers and data
   - First-person perspective with real examples
   - No corporate jargon
3. **If FOUNDER_CONTEXT.md exists**, blend the founder's brand voice with the voice DNA from the reference posts
4. **Draf