---
name: pain-first-social-post
description: Writes short social posts that open on a painful reality the reader already lives, agitate it with named devices, and introduce the product late as relief rather than as the entrance. Carries the hook rules, a banned-openings list, a device bank, four bridge moves and six structural patterns for producing variants that differ from each other. This skill should be used when writing social posts about a product or a single feature, particularly when several posts are needed for one launch.
---

# Pain-first social posts

## The claim this skill is built on

Asked for an engaging post about a feature, the default output is an advertisement with a metaphor in line one and the product name in line two. Both moves are individually defensible and together they tell the reader, in about a second, that this is a pitch. Everything after that is unread, which is why the post gets no engagement and why the diagnosis afterwards is always about the wrong thing, the hashtags or the time of day.

The claim is narrow. A post of this kind is a sequence in which the product arrives last, and the sequence is decided entirely by line one. If line one is a fact the reader recognises, they read line two to find out whether you actually understand it. If line one is a comparison, a rhetorical question or a promise, they have already classified the post and the rest of your specifics are wasted on nobody.

Two boundaries, so this file stays in its lane. It generates posts rather than checking one that exists. And the anti-tell material here is scoped to the opening line and the shape of the post. The sentence-level vocabulary pass, the one that hunts banned words and punctuation across a finished draft, is a separate job done after the variant is chosen.

## Step 1, the input check

If the product or feature is not named, ask exactly three things and write nothing until they come back:

1. The product, or the specific feature.
2. The audience.
3. The specific pain.

For a single feature, the pain is the pain of operating **without** it. This is the reframe people skip, and skipping it produces the most common bad brief in this format: a description of what the feature does, handed over with a request for a post, leaving nothing to agitate. A feature that stops double-bookings is not the subject. The afternoon you spent apologising for one is the subject.

Three questions is the ceiling. Asked more than that, a request turns into an interview and the person stops answering. If only the product is given, infer the audience and the pain, state the inference in one line, and start drafting. A stated inference is easy to correct. A question is easy to abandon.

## Step 2, restate the subject in one line

Write down, before drafting: this post is about [thing] for [audience], and the pain is [pain].

This exists to stop style-reference bleed. If you have just read three example posts about a different product, the draft slides back towards that product with the nouns swapped, and the result is a post about somebody else's problem wearing your product's name. The one-line restatement is the cheapest available guard and it takes ten seconds.

## Step 3, find the pain as a moment

Not a category. A moment.

**The moment test.** Can you name the time of day, the object on the screen, and what the person did next? If you cannot name at least two of the three, you have a category and the post will be abstract no matter how it is worded.

| Category, which does not work | Moment, which does |
|---|---|
| Teams waste time on manual scheduling | You offered Thursday at three to two people. The second one accepted first |
| Invoicing is inefficient for freelancers | The client asks for the invoice you sent in March. You have three folders called invoices |
| Onboarding new staff is painful | Day one, and the new starter is waiting for someone with admin rights who is on leave until Tuesday |

The moment is also what makes the post checkable. A reader either had that afternoon or did not. A category is something they can agree with while feeling nothing.

## Step 4, set the audience width

**Default wide.** These pains are usually more universal than the person briefing the post believes, because they are living inside one job and the pain belongs to twelve.

The mechanism is mechanical rather than mysterious. Every job title, tool name and piece of jargon in the opening lines removes the readers who would have nodded but do not use that tool or hold that title. Reach is quietly shrunk at the top of the post and nobody attributes the missing readers to the noun that lost them.

**Decision rule.**

- **If the pain only exists once the tool exists**, go job-specific. Somebody who has never used the category cannot recognise the moment, so a wide frame buys nothing.
- **If the pain exists for anyone who ever did the manual version**, go wide. Lead with the version any member of the broad audience recognises, then ground it in exactly one concrete example, and let the example carry the specificity instead of the frame.
- **If you cannot tell**, write the wide version, then delete the single most job-specific noun in line one and read it again. If it still parses and still stings, keep it wide, the noun was decoration. If it collapses into vagueness, that noun was carrying the pain, and the post goes job-specific.

## Step 5, hook discipline

This is where machine-written attempts identify themselves, and it is the part of the file that decides the most.

**Six rules.**

1. Line one states the painful reality plainly, as a fact the reader already lives.
2. Open with one of four things: a fact, a number, a real object somebody could screenshot, or a moment with a time attached to it.
3. **No simile and no metaphor in line one.** Analogies are useful and they belong in the middle, during agitation. In the opening they announce a writer at work.
4. Show the reality, do not label it. "It is so frustrating when" is a label. The frustration is supposed to be the reader's conclusion, not your instruction.
5. If a line feels crafted, cut it. Read it aloud. Anything that sounds written was written.
6. Line one earns line two, and line two must add information rather than restate line one in different words.

**Banned openings.** These are not weak, they are pre-classified. A reader has seen each of them several hundred times and knows what follows.

- "Every morning I"
- "Let me tell you about"
- "Picture this"
- "Imagine if"
- "Here is the thing"
- "I used to think X. Then Y."
- "Unpopular opinion:"
- "Hot take:"
- "Confession:"
- "Nobody talks about"
- "X is broken. Here is why."
- "Ever wonder why"
- "Raise your hand if"
- "This might be controversial, but"
- Any question the reader did not ask
- Any sentence describing what the post is about

One exemption. A dated opening of the form "It is 2026 and [specific true thing]" survives only if the thing after "and" is a checkable object rather than a complaint. The date is doing nothing. The object is doing all of it.

## Step 6, amplify, without naming the product yet

The device bank. Pick two or three per post, not all seven.

**1. The exact painful moment.** Extend the moment from step 3 by one beat: what the person did in the following thirty seconds.

**2. The escalating list of absurd workarounds.** Three to five items, ordered by increasing absurdity, and the last one should be true and mildly humiliating. "You keep a second calendar in your head" is the register.

**3. The shared enemy.** The status quo, the incumbent category, or the dumb manual process. Never the reader. Never a named company, and never a named person, which is a legal and reputational cost as well as a dating problem, since the named competitor changes and the post does not.

**4. Comedic specificity.** A precise number beats a vague complaint. Calibration matters: the number has to be plausible enough to be real. Forty-one open tabs is funny because it might be true. Four thousand open tabs is a joke about the writer. Where an invented number could be mistaken for data about your own product, it is not a device, it is a false claim, so keep invented specifics on the pain side and never on the results side.

**5. Typographic emphasis, for tone.** One word in capitals, a line break used as a beat, a one-word line. Use it twice at most. Note that platform-native bold on several networks is Unicode substitution rather than formatting, which breaks screen readers and search, so tone emphasis should be capitals and line breaks rather than substituted glyphs.

**6. Quoting the villain.** One line of dismissive dialogue in quotation marks, from the process or the category rather than from anyone real. "The system is working as intended."

**7. Personifying the broken thing.** Give the process an attitude that fails. "The calendar would like you to know it has no opinion about your reputation."

## Step 7, the bridge, four moves

The product arrives as relief. Four ways in.

**The early parenthetical whisper.** The product mentioned in brackets, mid-post, in a lowered register. Use when the audience already knows you sell something and pretending otherwise would be coy. This is the one permitted exception to the past-the-halfway-point rule, and it has to be genuinely parenthetical: if the bracket contains a benefit list, it is an advertisement in a costume.

**The last-line punchline.** The product is where the joke lands. Use when the escalation has been comedic and the reader is expecting a payoff anyway.

**The closing note tied to a feeling.** Not the feature, the feeling it removes. "We built it so nobody has to spend an afternoon on that email again."

**The reveal.** "So we built the thing they should have shipped." Effective and self-limiting. Use it rarely, because a person who reveals a new product every fortnight is not revealing anything.

**The test that applies to all four.** Delete the product line and read the post. If it is still worth reading, the bridge is relief. If it collapses into nothing, the post was an advertisement with a preamble and the reader worked that out earlier than you did.

## Step 8, arc and length

The shape, in order: the plain hook, the line that earns it, escalation with specifics and varying line length, one sharp analogy or reframe in the middle, the low-key product mention past the halfway point, a payoff line, a low-friction question.

**Length.** Roughly 90 to 220 words for the standard shape. A flat three-line micro-post reads as filler unless it is a genuine one-liner with a real joke in it. Earn the length with specifics rather than adjectives, and apply the test literally: every line you add should introduce a noun, a number or an object. A line that adds only adjectives is padding and the reader feels it as slowing down.

**Truncation.** Most feeds show only the first couple of lines before a cut, so lines one and two are the entire advertisement for everything below. The exact cut point differs by network and by device and it moves without notice, so check it in the composer rather than trusting a number.

**The closing question.** Low friction. "What is yours?" gets replies. "What are your thoughts on the future of scheduling?" gets none, because answering it is homework. Keep it under about twelve words and make it answerable in four.

## Step 9, produce three to five variants, each on a different pattern

Not three drafts of the same post. Different structures, each labelled with its pattern, each formatted exactly as it would publish, line breaks included.

**The underused-feature secret.** The unglamorous thing nobody demos, and the moment it quietly saves. Works because it reads as insider information rather than as marketing.

**The subverted good-news announcement.** Opens in the register of an announcement, then turns into the pain. The reader's guard is up for a pitch and down for a confession.

**The love-hate letter to the incumbent.** Genuine credit first, specific unfixed thing second. The credit has to be real or the whole post reads as a hit piece, and the incumbent is a category, never a named company.

**The borrowed non-post format.** A job advert, an obituary, a press release, a support ticket, an out-of-office reply, a changelog entry, a set of terms and conditions. The product mention goes inside the format: as the salary line, as the survived-by line, as the resolution field. This pattern is the most enjoyed and the most often ruined, and it is ruined in exactly one way, by breaking the format at the end to sell. Stay in character to the last line.

**The migration list.** Ten pairs of the form "old thing, new thing" that the reader already believes, with your product as the final pair. The first nine must be true and have nothing to do with you, because the list is borrowing agreement and you spend it once.

**The analogy flex.** Describe a delightful version of a normally dreaded experience, a dentist appointment that took four minutes, a passport queue that moved, then transfer it. This is the one place a sustained analogy is correct, and it still may not appear in line one.

## Step 10, the self-check

Run every variant through this. The first six are mechanical.

- Line one contains no simile marker: no "like", no "as if", no "feels like".
- Line one contains no product name.
- The product first appears past the halfway point, unless this is the declared whisper variant.
- Zero em dashes.
- No banned connective: "here is the thing", "let that sink in", "read that again", "and that is the point", "the best part", "spoiler".
- It ends with a question of under twelve words.

Then the four that need reading:

- It names a moment, not a category.
- Line two adds information rather than restating line one.
- At least one shared-enemy or relatability device is present.
- Deleting the product line leaves something worth reading.

**The anti-slop catalogue, scoped to the opening and the shape.** The negated-then-corrected construction, "it is not X, it is Y". Perfectly balanced triads. Over-symmetrical parallelism, meaning every line the same length and the same grammatical shape, which is the strongest structural tell in short posts and survives any word-level edit. The tidy moral in the last line. Length padded with adjectives instead of specifics. This list is deliberately about hooks and arcs. Vocabulary-level cleaning is a separate pass, run afterwards on the chosen variant.

## Worked example

**Brief.** An invented scheduling tool. The feature: once a slot has been offered to somebody, it stops being offered to anybody else until the offer expires. Audience: anyone who books calls with people outside their own company. The pain, as a moment: two people were offered the same slot and the wrong one accepted first.

**Hook, rejected.** "Scheduling is like playing chess against yourself, blindfolded." Simile in line one, labels the pain instead of showing it, and names no object. It also fails the crafted test on the first read aloud.

**Hook, kept.** "You offered Thursday at three to two people. The second one accepted first."

**Variant B, the love-hate letter to the calendar, with a whisper bridge.**

> You offered Thursday at three to two people. The second one accepted first.
>
> Now one of them is getting the email. You know the one. It opens with "so sorry about this" and ends with four alternative times, three of which you have also already offered to somebody else.
>
> The calendar is not going to help you here. The calendar's position is that both meetings are fine. The calendar would like you to know it has no opinion about your reputation.
>
> So you do what everyone does. You keep a second calendar in your head. You hold slots you have not offered to anyone. You type PENCILLED in capitals into an event title, as though the software can read tone.
>
> (We got tired of that and built the hold into the booking page. A slot you have offered stops existing for everyone else until the offer expires.)
>
> Nobody puts that on a homepage. It is the difference between Thursday and an apology.
>
> What is the worst double-booking you have had to send that email about?

**Self-check on Variant B.** Line one is a fact with no simile and no product name. Line two adds the email, which is new information. Devices used: the exact moment, the escalating workarounds, the personified villain, one word of typographic emphasis. Bridge: the parenthetical whisper, declared. Deleting the parenthetical leaves a post that still works, which is the test passing. It closes on a question of eleven words. One repair was needed during drafting: the payoff line was originally "It is not a feature anyone puts on a homepage, it is the difference between Thursday and an apology", which is the negated-then-corrected construction from the catalogue, and it was cut into two sentences.

**Variant A**, the underused-feature secret, put the product in line four of nine and failed the halfway rule. **Variant C**, the borrowed format, was drafted as an out-of-office reply and broke character in the last line to add a link.

**Verdict: Variant B ships. Variant A is repairable by moving the product mention down three lines. Variant C is discarded rather than repaired, because a borrowed format that breaks character has already spent the only thing it had.**

## Failure modes

**The telegraphing hook.** The opening contains a setup the reader recognises as a setup, and the post is classified as an advertisement before the specifics arrive. From the outside it looks like a post with good content and no engagement, and the content is not the problem.

**Simile in line one.** The most common single defect, and the easiest to fix, because the fix is almost always the sentence that was going to be line two.

**Accidental niching.** A universal pain narrowed to one job title by a noun in the first line. The symptom is a post that performs well with a small number of very warm replies and reaches nobody new, and the missing readers are invisible, which is why this one persists.

**Product as the entrance.** The product named in the first two lines, so the pain reads as a pretext rather than as the subject. The tell in the comments is that people respond to the product rather than to the moment, which means only people who already know you read it.

**Machine tells in the shape.** Not the vocabulary, the shape: every line the same length, three-item lists everywhere, the negated-then-corrected sentence, and a tidy moral at the end. Each individually is fine, and together they are a signature that survives every word-level edit anyone applies afterwards.

**Style-reference bleed.** The post is about whatever example you were reading rather than about the subject, usually with the same devices in the same order. It reads as competent and slightly hollow, and the person who briefed it says it does not sound like them without being able to say why.

**Punching down.** The shared enemy quietly becomes the reader: "you are still doing this by hand?" The symptom is defensive replies explaining why they do it by hand, which is the opposite of the intended reaction and is very hard to recover from in the same thread.

**The invented first-person anecdote.** A story that did not happen, written as though it did, under a real person's name. It works until one person asks a follow-up question about the story and there is no second detail. This is the only failure in this list with a cost beyond engagement, and the fix is to write the moment in the second person, describing something that genuinely happens, rather than as a memory you do not have.

**The flat micro-post.** Three short lines and a product mention, published because it looked clean. With no escalation and no specifics there is nothing to feel, and it reads as filler in a feed that is already full of filler.

## What this skill does not do

- It cannot verify that the pain is real. It will amplify an invented pain just as willingly as a real one, and readers can tell the difference faster than any internal reviewer can.
- It does not check platform mechanics: truncation points, character ceilings, link handling, hashtag counts and the Unicode formatting that breaks screen readers are all a separate pass.
- It does not do the sentence-level vocabulary pass. The catalogue here covers hooks and shapes, and a chosen variant should still be run through a word-level check before it goes out.
- It cannot post, schedule, or tell you when to publish, and it has no access to what your audience has already seen from you, which is what decides whether a device is fresh or is your third obituary this quarter.
- It has no view on whether the feature is worth a post at all. Some features are documentation, and the honest answer is a changelog line.
- It will not make an unremarkable product remarkable. The devices amplify a pain that already exists, and where none does, the output is a well-structured post about nothing.