⚠️ Design system CSS not found. Check the path in docs/docs.config.js → designSystemPath, then re-run npm run docgen.

Hooks

The mechanics of a scroll-stopping first line

Content strategy / Hooks

The repeatable mechanics behind a scroll-stopping first line, pulled from the 1,000 Viral Hooks reference and translated into my voice and rules.

This sits under the Performance Playbook. The Playbook says "confession or claim in the first line." This file is the how.


The one rule

The first line carries the punch. No warm-up, no meta, one idea.

The whole library of 1,000 hooks comes down to this. They make the claim first and earn it after. They never say "this is hard to admit" before the admission, they just admit it. They never say "stay with me," they make you stay by opening a loop you have to close.

My failure mode is the opposite: I earn the claim before I make it. Calm is the brand, but calm is the delivery, not the structure. A calm voice can still lead with a sharp line. Lead with the verdict, let the vulnerability be beat two.


The 4-point hook test

Run every hook through this before it gets recorded. If it fails two, rewrite it.

  1. Concrete. Is there a number, a name, or a specific image in the first line? "15 years", "Netflix", "one typo in permanent print" beat "a long time", "big brands", "an early mistake".
  2. Open loop. Does the first line force the second? If someone could nod and scroll, there's no loop. "This is why no one remembers you" works because you need the why.
  3. One idea. One clause, not three stacked. If there are two commas before the point lands, it's too slow for the first three seconds.
  4. Only I could say it. Identity-first, not topic-first. A marker, a confession, or a verdict that's mine. This is what keeps it on-brand and repels the wrong audience.

The engines (mapped to my pillars)

Pick the engine that fits the idea, then pour the payload in. These are the patterns that recur most across the 1,000.

  • The open loop / withheld answer. State a consequence, hide the cause. "This is why your campaign got ignored." Best for: invisible design, AI takes.
  • Time compression. A number against a clock. "It took me 10 years to learn this. I'll give it to you in 60 seconds." Best for: AI frameworks, building the business.
  • The named target. "If you lead a creative team and you're tired of work slipping, this is for you." Repels students and job-seekers on purpose. Best for: anything industry-facing.
  • The contrarian / myth bust. A verdict against the consensus. "Reach is vanity." "AI isn't the craft." Best for: designed participation, AI, hot takes.
  • Loss aversion. Frame the cost of not knowing. "You're losing the thing you spent the budget earning." Best for: designed participation, invisible design.
  • Before / after authority. "I went from this to this." Concrete transformation, no adjectives. Best for: building the business, dyslexia story.
  • The confession with stakes. A real risk said plainly. "I don't have a backup plan, so this needs to work." Best for: building in public, dyslexia, the camera-fear thread.
  • The concrete contrast. "This is what it looks like when it's designed. This is what it looks like when it's not." Best for: breakdowns, invisible design.

For worked examples of every engine built from my real story bank, and a deeper build-out of the human engines (story, confession, day-in-the-life, curiosity) plus a list of patterns to refuse, see Hook-Library.md.

A note on staying on-brand: I do not put others down to make a point (no "everyone else is doing it wrong"). The contrarian engine targets a belief or a consensus, never a person. Anchor the loss-aversion engine in a real client problem, not a manufactured fear.


Quick reference: warm-up words to cut

These delay the claim. If a hook opens with one, the real hook is usually the line after it.

  • "This is uncomfortable to say…"
  • "Stay with me…" / "Let me explain…"
  • "I'll be honest…" / "Honestly…"
  • "So, this is me…"
  • "If you're someone who feels a bit…" (the feeling is fine, the hedging "a bit" is not)
  • Any sentence describing the statement instead of making it.

The highest-leverage edit

Delete the first sentence and see if the hook got better. Most of the time it will have: the punch is usually sitting in sentence two or three with a warm-up in front of it. (The launch-batch audit that proved this is banked in 02 Skills/_archive/Hook-Audit-2026-07.md.)

On this page
  • The one rule
  • The 4-point hook test
  • The engines (mapped to my pillars)
  • Quick reference: warm-up words to cut
  • The highest-leverage edit
Previous

Story arcs

Next

Formats

© 2026 By Default