Skip to content

0xF4ng/aether-growth-fieldwork / growth/short-form-social

short-form-social

Verified

FileKindSize
SKILL.mdskill md12.2 KB
references/hooks-and-formats.mdmarkdown4.8 KB

references/hooks-and-formats.md

View on GitHub
# Hook Patterns + Per-Platform Formats

Detail for [`../SKILL.md`](../SKILL.md) Steps 1–2. Read when building a hook or shaping a post.

The platform norms here **defer to** `growth/DOMAIN.md` (distribution norms) and `pmm/content-review/SKILL.md` (platform-format discipline) as the single source of truth — this file applies and exemplifies them for short-form authoring, it does not redefine them.

---

## Hook patterns (the first line)

The hook is the highest-leverage atom because the reader decides to continue or scroll within the first ~8 words. The rule across all patterns: **the first line carries a complete tension, claim, or fact, with no setup required.** If line one needs line two to make sense, it isn't a hook yet.

### Pattern 1 — Specific number
A surprising concrete metric, first thing.
- Weak: "We made our monitoring a lot better."
- Strong: "We deleted 39 of our 40 alerts. Incident response got *faster*."
- Best for: results, before/after, anything you can quantify.

### Pattern 2 — Counterintuitive claim
A defensible claim that cuts against the default belief. Must be one you can actually back — a contrarian hook with no substance is bait.
- Weak: "Dashboards are important for observability."
- Strong: "Most dashboards are decoration. I've built four; three were never opened after the demo."
- Best for: opinion, authority, thought leadership.

### Pattern 3 — Named pain
The reader's exact situation, in their words — they recognize themselves instantly.
- Weak: "Debugging production issues is hard."
- Strong: "It's 2 a.m. and you're scrolling pg_stat_statements by hand trying to find which query just took down checkout."
- Best for: reach within a specific ICP; the more specific, the more it travels within that group.

### Pattern 4 — Before/after gap
The distance between two states, stated plainly.
- Strong: "47 minutes to find the bad query. Now it's 3. Here's the one change."
- Best for: migration stories, improvement narratives.

### Anti-hooks (don't)
- Manufactured curiosity: "You won't believe what happened when…"
- Meta-throat-clear: "Here are my top 5 takeaways 🧵" / "Thread 👇"
- Vague generality: "In a world where AI is changing everything…"
- The hook that needs setup: anything where line one only makes sense after line two.

(These map directly to ai-slop-audit Family 1 and content-review's opener checks — a hook failing here also fails those gates.)

---

## Per-platform formats

### LinkedIn
- **Opener:** a practitioner observation, question, or data point — not manufactured curiosity. The first line works standalone (preview truncation).
- **Length:** 150–300 words for thought leadership; story-driven can run longer if justified.
- **Structure:** opener → one insight, developed → optional single CTA. Opinion grounded in evidence/experience *before* it's asserted.
- **CTA:** at most one, specific and low-friction ("the full write-up is in the first comment"), or none. Never multiple competing asks.
- **Don't:** hollow-enthusiasm openers, "Comment YES", inline hashtag spam, multiple CTAs.

### X — single post
- The whole post is hook + one payload. The hook stands alone.
- Within the character limit; no warm-up; no thread-bait if it's meant to be single.
- One claim, one payload. If it needs more, it's a thread.

### X — thread
- **Tweet 1** is a standalone hook (one of the patterns above) — readable and compelling with none of the rest. It is *not* "here's a thread about X."
- **Each subsequent tweet** carries exactly one fact / observation / step. ~200–240 chars.
- **No thread numbering** (1/, 2/…) and no "🧵" — let the content pull the reader down.
- **Last tweet** = the takeaway or a soft CTA.
- **Links go in the first reply,** not the body (body links get reach-throttled ~25%). First reply: "Full write-up → [link]."
- **No "Here are my N takeaways"** opener — lead with the sharpest single claim the thread proves.

### Cross-posting rule
Choose the platform, then write to it. The same idea becomes a *different artifact* on LinkedIn vs X — different length, different opener, different CTA placement. Lifting a LinkedIn post verbatim onto X (or vice versa) reads as native to neither. See SKILL Step 5: write one story, adjust the frame.

---

## Repurposing a longer piece (frame, don't fragment)

When the source is an essay or newsletter issue:
1. Find the **one** observation that is the piece's spine (the thing it proves).
2. **X thread:** that spine becomes tweet 1; the supporting beats become one-idea tweets; the essay's closing worldview becomes the last tweet.
3. **LinkedIn:** foreground the practitioner angle of the spine; one insight, ~200 words.
4. **X single:** sharpen to the single hardest claim the piece can defend.

Same truth, surface-shaped — never separate stories, never the long piece truncated mid-argument.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall