# Arcs, specifics, platform framing + two worked examples

## Arc structures (pick by goal)
| Structure | Shape | Best for |
|---|---|---|
| **BAB** | Before (pain) → After (better) → Bridge (how) | offers, transformations, product value |
| **3-Act** | setup → turning point → resolution | most posts, Reels, case studies |
| **Hero's Journey** | call → struggle → return changed | founder/origin, longer video |
| **StoryBrand** | customer-hero + brand-guide + plan → success | brand messaging, landing-page-style posts |

## Specificity technique (vague → concrete)
```
"We help businesses grow."            -> "Last March a 2-person bakery messaged us at midnight, panicking about a 400-order weekend."
"I was overwhelmed."                  -> "Shoulders tight, jaw clenched, staring at a dashboard at 2 AM, coffee gone cold."
"Customers love our product."         -> "She texted a photo of the empty tray with one word: 'gone.'"
Rule: one true, specific, sensory detail creates presence. Show the scene; don't summarise the feeling.
```

## Platform framing (same story, different framing)
```
TikTok:    personality + vulnerability; talk to camera; fast micro-arc; relatable > polished
LinkedIn:  professional transformation / lesson learned; "here's what we got wrong and what changed"
Instagram: visual-first; a 5-7 frame carousel = a complete arc (cover = setup, last = payoff)
YouTube:   longer emotional arc; clearer 3-act; let tension build
Threads/X: short written arc; one tension, one turn, one line of meaning
-> Keep the narrative VOICE consistent across all of them (recognition > visual sameness).
```

## Serialized storytelling (compounds)
```
A 6-post launch series, a monthly "what we got wrong", a weekly customer-transformation -> anticipation + return visits.
Map the arc in the content-calendar so it has a real beginning/middle/end (don't let it trail off after post 2).
```

## Metrics + WoopSocial flow
```
STORY METRICS: saves, shares, comment length, profile visits -- NOT likes ("40 likes/200 saves > 400 likes/3 saves").
FLOW: agent finds + structures the story -> format writer builds it (reels-script/carousel-writer/linkedin-post-writer) +
hook-writer for the open -> visual via image tools/design-and-templates -> WoopSocial publishes (series mapped in content-calendar).
WoopSocial does NOT generate the story or judge resonance.
```

## Worked example 1 - SaaS founder, LinkedIn (blunt indie-founder voice)
```
Real story: we shipped a feature nobody used. Arc (3-act): setup (we were proud of it) -> turning point (0 adoption, one brutal
user call) -> payoff (what we learned + the rebuild that worked). Specific: "a user said 'I genuinely don't understand what this
does' on a Tuesday call -- I muted and stared at the wall." Meaning: ship the problem, not the feature. linkedin-post-writer builds it. Metric I watch: saves + comments, not likes.
```

## Worked example 2 - bakery, Instagram carousel (warm studio voice)
```
A true customer moment, told as a 6-frame carousel. Frame 1 (setup): a midnight message before a 400-order weekend. Middle frames:
the scramble, the early mornings, the small fix that saved it. Last frame (payoff): the empty tray and a one-word text -- "gone."
The hero is the customer, we're just the guide. carousel-writer lays it out, the cover does the hook. We watch saves + shares. Nothing invented -- it really happened, shared with permission.
```

Both: a TRUE story; a clear arc with the customer as hero; one concrete sensory detail; one line of meaning; built by the
right format writer; measured by saves/shares. Nothing fabricated.


---
资料：Frank Heijdenrijk / pavelhov/social-media-skills

原始版本：https://github.com/pavelhov/social-media-skills/blob/1680b37bf0dc32b52da247a8196ef27a6cd47bd4/skills/storytelling-and-narrative/references/arcs-formats-and-specifics.md

许可：MIT。目录与内部链接已经整理，未收录图片已省略。

MIT License

Copyright (c) 2026 Frank Heijdenrijk

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.