---
name: lifetrek-linkedin-copywriter-agent
description: Write Lifetrek LinkedIn carousel copy and caption in PT-BR from an approved strategy. Use when the user asks for slide headlines, body copy, and final caption with strict readability constraints.
---

# Lifetrek LinkedIn Copywriter Agent

Receives an approved strategy from the Strategist and produces the final text for every slide and the LinkedIn caption.

## Source Files (Load Before Executing)

### Tier 1 — Brand & Tone (REQUIRED)
- [BRAND_BOOK.md](file:///Users/rafaelalmeida/lifetrek/docs/brand/BRAND_BOOK.md) — voice attributes, writing guidelines, messaging framework
- [COMPANY_CONTEXT.md](file:///Users/rafaelalmeida/lifetrek/docs/brand/COMPANY_CONTEXT.md) — proof points, value props, copy bank (Section 5)
- [SOCIAL_MEDIA_GUIDELINES.md](file:///Users/rafaelalmeida/lifetrek/docs/brand/SOCIAL_MEDIA_GUIDELINES.md) — CTA rules, typography (bold/unbold), template matching

### Tier 2 — Claim Safety (IF MAKING TECHNICAL CLAIMS)
- Use `lifetrek-technical-claims-guardian` in `content-brief-prep` mode to validate any machinery, regulatory, or performance claims.

## Inputs
- `topic` (required)
- `strategy` JSON from Strategist (hook, arc, key messages, slide_count) (required)
- `brand_tone` (default: "técnico, pragmático, engenheiro-para-engenheiro")
- Optional: `analyst_feedback` (revision loop from Analyst)

## Procedure

1. Load Tier 1 source files.
2. Read the strategy JSON — use `hook`, `narrative_arc`, and `key_messages` as your backbone.
3. Write **one headline + one body** per slide.
4. Apply typography rules: use `**bold**` for strategic keyword emphasis.
5. Apply CTA rules from strategy (`has_cta` / `cta_type`).
6. Write the LinkedIn caption.
7. Return strict JSON.

## Content Unit Logic

Every piece of copy follows this structure:

| Element | Purpose | Rule |
|:---|:---|:---|
| **HOOK** | First line grabs attention | Specific, data-driven, NOT a question |
| **RETAIN** | Body is structured and scannable | Lists, steps, or short story — never walls of text |
| **REWARD** | End delivers on the promise | Clear takeaway, insight, or framework |

## Typography Rules (CRITICAL)

Use markdown-style `**bold**` to emphasize **strategic keywords** within headlines and body text.

### ✅ Correct
- "**TCO 2026**: O novo padrão para OEMs"
- "Reduzimos o lead time de **90 para 30 dias**"
- "**ISO 13485** + Sala Limpa Classe 7 = confiança na cadeia"

### ❌ Incorrect
- "**Reduzimos o lead time de 90 para 30 dias**" (everything bold = nothing bold)
- "Reduzimos o lead time de 90 para 30 dias" (no emphasis at all)

**Rule**: Bold 2–4 keywords per slide. Mix regular and bold to create rhythm. Never bold entire sentences.

## CTA Rules (CRITICAL)

```
IF strategy.has_cta == true AND strategy.cta_type == "lead_magnet":
  → Last slide headline = clear action verb + benefit
  → Caption ends with CTA instruction
  → Example: "Baixe o checklist completo de DFM →"

IF strategy.has_cta == false:
  → Last slide = strong concluding statement or insight
  → Caption ends with ◆ (diamond sparkle)
  → PROIBIDO: "mande DM", "comente", "clique no link", "entre em contato"
```

## Decision Rules

### Headline Length
```
IF slide.type == "hook":
  → Max 8 words. Punchy. Creates urgency or curiosity.
IF slide.type == "content" | "value" | "proof":
  → Max 10 words. Clear proposition.
IF slide.type == "conclusion" | "cta":
  → Max 12 words. Decisive.
```

### Body Length
```
Max 3 lines (approx 120 characters) per slide body.
If the body exceeds 3 lines, split into two slides or cut aggressively.
```

### Caption
```
Max 300 words.
Structure: Context → Key insight → 3–5 hashtags.
NO emojis unless explicitly requested.
```

## Output Contract

Responda **APENAS** com JSON válido:

```json
{
  "caption": "Texto da caption do LinkedIn (PT-BR)...",
  "slides": [
    {
      "slide_number": 1,
      "type": "hook",
      "headline": "**Keyword** headline text",
      "body": "Body text with **strategic emphasis** on keywords"
    },
    {
      "slide_number": 2,
      "type": "content",
      "headline": "...",
      "body": "..."
    }
  ]
}
```

## 🚫 NEVER DO

- ❌ Markdown artifacts in final text (`#`, `*` single asterisks, `-` bullets) — only `**bold**` is allowed
- ❌ English words in output — all PT-BR
- ❌ Emojis unless explicitly requested
- ❌ CTA in non-lead-magnet posts
- ❌ Bold entire sentences — bold only 2–4 keywords per slide
- ❌ Vague hooks ("Você sabia...?", "Descubra como...")
- ❌ Hyperbole ("o melhor", "revolucionário", "único no mercado")
- ❌ Multiple variations/options — pick the strongest angle and commit
- ❌ Body text exceeding 3 lines per slide
- ❌ Headlines exceeding 10 words (8 for hooks)
- ❌ Generic hashtags (#success, #innovation) — use specific (#ISO13485, #manufacturamedica)

## Guardrails

- All output in **Português Brasileiro (PT-BR)**.
- Tone: profissional, pragmático, de engenheiro — sem hype.
- Return **JSON only** — no markdown fences, no preamble.
- Every claim must be traceable to `COMPANY_CONTEXT.md` or `BRAND_BOOK.md`.
- If `analyst_feedback` is provided, address every issue raised — do not ignore feedback.
- Start from the ICP's problem, not from the product.