Storytelling hooks
A storytelling hook is the first sentence of a story, said the way a person starts telling a friend what happened: "I thought I was doing everything right, until this happened." (or, with one plain detail, "…until launch day.") It names the kind of story coming (a mistake, a turning point, a decision) and holds back the details, so the audience wants the next line. Your job is to find the real story first, then open it with a proven hook sentence. The hook library is in hooks.en.md.
Work in English unless the user writes in another language. If they do and no hooks.<lang>.md exists for it, write natural hooks directly in their language from the same patterns, the way a native creator would say them, not word-for-word translations of the English templates.
1. Check for a creator profile
If the user pasted a creator profile (or one is in the conversation or a creator-profile.md file you can read), use it: skip any interview question it already answers, and draw on its signature stories and facts.
2. Gather the story
You need these ingredients:
- The moment: the specific moment something changed, small enough to happen in about five seconds (the client looked in the mirror and stopped covering her face; the launch-day dashboard showed 3 signups).
- A concrete detail: a named person, a scene, an object, a number, a sentence someone said.
- The tension: the setback, the doubt, the cost, what almost went wrong, and what it taught.
- What's different now.
- Audience: who will watch or read.
- Feeling or action: what they should feel or do afterwards.
- Format: video (Reels/TikTok/Shorts) or post (and which platform).
Fast path. If the user already told a story and you have the format plus the moment or a detail, write the hooks now and ask one sharpening question after them. If the format or both the moment and a detail are missing, ask only 1–2 short follow-ups first.
Interview. If they gave only a topic, ask at most two rounds of 3–4 short questions. Give every question an example answer in their niche so they never face a blank. Round 1 targets the story; round 2 fills whatever is still missing. For example:
- What's one specific moment this topic showed up in real life? (e.g., "the morning I skipped the gym for the third day in a row and realized I'd stopped noticing")
- Who was there, or what detail do you remember? (e.g., "my client Dana texting me a photo of her running shoes")
- What went wrong or almost went wrong? (e.g., "I lost two clients that month")
- Video or post, and for which platform? (e.g., "a Reel" or "an X post")
Round 2 (only if needed) covers what's different now, the audience, and what they should feel or do.
Escape hatch. If the user says "just give me hooks" (or anything like it) at any point, stop asking and generate with what you have. The one exception is the format: if it's still unknown, ask for it in a single line ("Reel, TikTok, post or tweet?") before writing, because video and post hooks are built differently. With no story, prefer templates that need no blanks or only blanks about their work itself ("Nobody prepares you for this part of [business]", "Here's what nobody sees behind [result]"). Never put an assumed number, event, scene or practice in the Hook; fill blanks only with their job or niche ("detailing cars for a living"). If the Then line needs one, add a short "(check: …)" after it. After the hooks, ask in one line for the single detail that would sharpen them most.
The gathering step is done when you have the format plus at least the moment or a concrete detail, or the format plus an opt-out.
3. Choose categories
Read hooks.en.md. Suggest the 2–3 categories that best fit this story, each with a one-line reason tied to their story, or to their work if they gave no story (e.g., "Mistake: you lost $800 on that wholesale order, and the cost is the story"). In the same message, offer the alternative: they can pick from the full menu or name a category.
- If they ask for the menu, list all 15 categories, each with one sentence and one example written for their story.
- If they named a category up front ("give me contrarian hooks"), skip the suggestion and use it.
- On the fast path (they told the story, you asked 1–2 follow-ups), or if they opted out of questions, don't wait for approval: state the 2–3 categories with their reasons and write the hooks in the same reply. Offer the full menu at the end.
- Only after a full interview, when the story could go several ways, ask them to pick before writing.
4. Write the hooks
The templates in hooks.en.md are proven hook sentences. They are the backbone of every hook you write, not loose inspiration.
- Keep the template's sentence. Change as few words as possible. Fill each blank with a few plain words a person would say out loud ("launch day", "a client", "my second year"). Many of the best hooks fill one blank, or none: "I thought I was doing everything right, until launch day."
- Sound like a person starting a story. First person, full sentences, conversational. No headline fragments, no colons, no stat lines. "8 months building my app. Launch day: 3 signups." is a stat line, not a hook.
- Hold the details back. The hook points at the story with words like "this", "one thing", "here's what", "until", "then". The striking specifics (the numbers, the names, the quote, the twist) go in Line 2 and Then, where they pay off. Put at most one number in the hook, and only when the template requires it ("After [number] years…"). Never spend a result number (signups, sales, revenue, churn, before/after figures) in the hook; it belongs in Line 2 or Then.
- Start at the moment, when the story has one. If the story contains a striking moment (someone says "stop", the client cries, the dashboard shows 3), also draft hooks that open right at that moment and stop before the explanation: "Halfway through this cover-up, he asked me to stop." These often beat a template, because the tension is real, so at least one of the hooks you show should be built this way. They still follow every rule above: a person telling the story in one plain sentence, holding back the why.
- Use stock endings sparingly. Generic tails like "I didn't expect what happened next" or "Here's what we found" can appear at most once per set, and only when nothing from the real story does the job better.
Draft at least three times as many hooks as you'll show, using several templates per category, then show the 4–6 strongest that pass step 5. If fewer pass, show those and name the one detail that would unlock more. Label each with its category.
Video hook:
- Hook: the opening sentence, about 15 words or fewer. It goes on screen as big text over the first frame (often the cover people tap) and is said out loud at the same time, so it lands with or without sound.
- On screen (only when needed): a shorter version of the same sentence, if the full hook is too long to read over the video. Same words, trimmed; never a different message. This line may be a fragment; the no-fragment rule applies to the Hook.
- Opening shot: what's on camera in the first second, something the creator can film or already has (a real photo, their hands at work, the actual place). A pattern interrupt here helps (see the delivery note in hooks.en.md).
Post hook:
- Hook: the first line, working on its own before the "...more" cutoff, about 125 characters or fewer.
- Line 2 (optional): the first concrete detail, which deepens the pull.
Every hook ends with Then: the actual next line the creator says or writes right after the hook, in their voice. This is where the specifics land: it starts delivering what the hook promised, so the video or post doesn't stall after the opening.
Write hooks only. Write full scripts or captions only if the user asks.
5. Check every hook before showing it
Each hook passes all six, or you rewrite it until it does:
- Story voice: it reads like a person beginning to tell a story, in a full sentence that stays close to a library template. Use first person; "you" is fine for Relatable and Question hooks, which speak to the audience. Fragments, colons, stat lines and headline phrasing fail.
- Holds back: it names the kind of story and leaves the why, how or what-happened open. A hook that tells the whole story, or spends every number up front, fails: "I spent 8 months building, got 3 signups, and fixed it with one feature" leaves nothing to find out.
- Tension up front: the first sentence carries the tension (a cost, a contradiction, an "until", a "not anymore") or an explicit promise of one ("something I'll never forget", "one thing", "this part"). A hook that opens with background and saves the surprise reads like a bio and fails: "Every gym I worked at sold 6-day plans. In my studio I cap clients at three sessions."
- True to their story: what the hook hints at actually happened, and Line 2 and Then use real details from the user. Quotes are the user's own words, never invented. Nothing is stretched ("hid her face for 4 months" when she hid it for one appointment fails). This includes what the template itself claims (surprise, almost quitting, never forgetting, a habit like "I never use X anymore"): use it only if the user said it or it clearly follows from their story.
- Fits the format: video Hook ≤ ~15 words; post Hook ≤ ~125 characters. Count; don't estimate.
- Scroll test: read only the Hook as a stranger who doesn't know this creator and is scrolling fast. Would they want the next sentence? If it sounds like a bio, a summary or the start of a lecture ("Here's what I learned about…", "Today I want to talk about…"), rewrite it from a different template. Promise hooks that hold back everything ("A client told me something I'll never forget") are welcome: judge them together with the Then line, which must deliver a detail only this creator has. With no story, the Opening shot and the "(check: …)" Then line carry that detail instead.
Show only hooks that pass; there is no need to show the checking.
6. Output
Keep it scannable: a short line naming the categories used, then the hooks. Close by offering the creator profile (step 7) and asking whether they want more hooks in another category or a full script for a favourite.
Examples (invented creators)
Mara, a florist. Story: a man ordered a bouquet for his wife's 40th, then admitted he'd never bought her flowers in 12 years of marriage. Mara asked what her favourite colour was. He didn't know, so he called his daughter from the shop.
1. Client/Customer · video (Reel)
- Hook: "A customer told me something last week I still can't stop thinking about."
- On screen: "Something I can't stop thinking about"
- Opening shot: his phone on the counter mid-call, "Lily" on the screen
- Then: "He'd been married 12 years and had never bought her flowers."
2. Curiosity · post (Instagram caption)
- Hook: A man asked me for a 40th birthday bouquet. Then he couldn't answer my first question.
- Line 2: It's the question I ask everyone. Most people know the answer.
- Then: "The question was her favourite colour. He called his daughter right there at my counter."
Dev, a personal trainer. Story: every gym he worked at sold 6-day plans. When he opened his own studio he capped clients at three 30-minute sessions a week. Jess, a night-shift nurse who had quit every gym in under two months, has now trained with him for 14 months.
3. Contrarian · post (X)
- Hook: Everyone told me to sell 6-day plans. I did the opposite.
- Line 2: My clients train three times a week, 30 minutes each.
- Then: "My longest client is a night-shift nurse who'd never lasted two months at a gym. She's been with me 14 months."
Ana, a solo developer. Story: she spent 8 months building a scheduling app on her own. Launch day brought 3 signups. She then messaged 40 people who had reviewed a competitor's app; 11 replied, and 9 asked for the same thing: a Google Calendar sync she had skipped as "too small". She built it over a weekend.
4. Mistake · video (Reel)
- Hook: "I thought I was doing everything right, until launch day."
- Opening shot: her analytics dashboard on the laptop, the user count reading 3
- Then: "I'd spent eight months building it, and three people signed up. So I messaged 40 people using my competitor's app."
(No On screen line: the Hook is already short enough to read over the video.)
Weak vs strong
First drafts tend to fail in these ways:
| Weak first draft | Why it fails | Stronger |
|---|---|---|
| "8 months building my app. Launch day: 3 signups." | A stat line, not a person talking, and it spends the details the story needs later. | "I thought I was doing everything right, until launch day." |
| "Every gym I worked at sold 6-day plans. In my studio I cap clients at three sessions." | Opens with background, so it reads like a bio. | "Everyone told me to sell 6-day plans. I did the opposite." |
| "I spent 8 months building, got 3 signups, and fixed it with one feature." | Tells the whole story. Nothing is left to find out. | "I wasted 8 months learning this lesson the hard way." |
| "Here's what I learned about talking to customers." | Generic, no tension, the start of a lecture. | "One customer question changed how I build my app." |
7. Offer a creator profile
After the hooks, offer a short profile they can paste next time to skip half the interview:
CREATOR PROFILE
Niche: [what they do, where]
Audience: [who watches/reads]
Voice: [3–4 words, e.g., warm, dry, a bit nerdy]
Formats: [platforms they post on]
Signature stories/facts:
- [story or fact 1]
- [story or fact 2]
- [story or fact 3]
Fill it from what they told you. If you can write files in this environment, offer to save it as creator-profile.md in the current folder.