Stats
Actions
Tags
From ew
Guides writing story-driven newsletters using a 5-beat hero's journey structure. Useful for crafting narrative-first issues that build audience through emotional engagement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ew:newsletter-creativeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Dependency:** Read `core/anti-ai-rules.md` (all 8 sections including Section 0) before writing anything.
Dependency: Read core/anti-ai-rules.md (all 8 sections including Section 0) before writing anything.
Story-driven newsletters. Personal essays. Narrative-first issues where the writing itself is the product, not just the information inside it. This is the format where your voice either builds an audience or disappears.
The creative newsletter lives or dies on one thing: does the reader feel something? Not think — feel. Information can be found anywhere. A story that moves someone cannot.
Every issue that gets remembered follows the same underlying architecture. The reader is the protagonist. You are the guide. The issue is the journey.
The 5-beat newsletter structure:
1. Ordinary World (Opening) Start in the reader's life, not yours. Their problem, their frustration, their version of the situation. This is where you establish: this is about you, not me. The reader must see themselves within the first 3 sentences.
❌ "Last week I was thinking about productivity..." ✅ "You've read every morning routine article. You've tried the 5am wake-up. The cold shower. The journaling. And you still feel behind."
2. Inciting Incident (The Disruption) Something broke, changed, or revealed itself. A realization you had. An experience that cracked open a new way of seeing. A fact that changed how you think about the subject. This is where the ordinary world gets destabilized — and why the reader needs to keep going. It must arrive within the first 200 words. If it hasn't happened by then, you're throat-clearing.
3. The Woods (Middle — Complication and Stakes) This is where most newsletters fail. Writers get to the insight and immediately explain it. Resist. Make the reader earn it. Present the complication: the counterargument, the thing that made the answer harder to find, the thing you tried that didn't work. If you skip straight to the answer, there's no journey — just an answer. Answers are forgettable. Journeys aren't.
4. Key Knowledge (The Turn) The specific thing that changed everything. Not a vague lesson — a specific moment, decision, reframe, or fact. Specific is proof. "I realized mindset matters" is not a turn. "The day I stopped optimizing my mornings and started protecting my nights was the day everything changed" is a turn.
5. New Equilibrium (The Payoff) The reader's life after they take what you gave them. Not a summary of what you said — a picture of what changes when they apply it. End on the sharpest point, not a mirror of where you started. The conclusion is earned, not announced.
The first sentence is a critical component. Treat it as one. Every word after it depends on this sentence doing its job.
Hook types that work:
The Contradiction: State something true that shouldn't be true. "The most-read writers I know are the worst at reading their own work."
The Specific Scene: Drop the reader into a moment without setup. "It was 2am. The draft was 4,000 words. None of it was usable."
The Uncomfortable Truth: Say the thing people believe but won't say out loud. "Most newsletters are published to feel productive, not because the writer had something to say."
The Inversion: Flip the conventional advice. "Stop trying to find your voice. You already have one. It's the one you're suppressing."
What kills the hook:
Show, don't announce. "She was devastated" tells the reader what to feel. Write the thing that makes them feel it. ❌ "I was overwhelmed by the pressure." ✅ "I opened my laptop at 6am and closed it at midnight having written one sentence I didn't delete."
Character-centric structure. Even in a non-fiction newsletter, you are a character. Your past self, your current self, the people you reference — all characters. Give them specific needs, flaws, and turning points. A character with a flaw and a journey is interesting. A narrator dispensing wisdom is not.
The Ghost (backstory as engine). The most resonant newsletters have a ghost behind them — a past failure, wound, or wrong belief the writer is still working through. You don't have to name it explicitly, but it must exist. It's what gives the writing its weight. Without it, you're just clever. With it, you're human.
Causality, not chronology. Don't write "and then this happened, and then this happened." Write: "This happened, therefore this happened. This happened, but this was wrong, so this changed." Every beat should follow from the previous one by consequence, not just by time.
The re-engagement rule. After every 300–400 words, give the reader a reason to stay. A new turn. A specific detail that surprises. A complication that raises the stakes. If someone can stop reading at any point without feeling they'd miss something, the pacing is broken.
Paragraph as unit of thought. Each paragraph goes somewhere. It opens with a premise, complicates or advances it, and arrives somewhere the reader didn't quite expect. A paragraph that opens and closes in the same place is not a paragraph — it's a sentence dressed up.
Short sentences earn their weight when used sparingly. One punchy sentence after a longer run lands like a punch. Used every third line, it loses all force and reads like a writing tic.
No fractal summaries. Do not recap what you just covered. Do not preview what's coming. Write forward. The reader was there. They don't need a recap; they need the next beat.
Every newsletter makes a silent contract with the reader when they open it: spend time here and you will leave with something. The payoff must honor that contract.
What is your reader's takeaway? Not what did you cover — what does the reader now feel, know, or see differently? If you can't answer that in one sentence before you write the issue, you don't have an issue yet. You have a topic.
The payoff must be specific. ❌ "The lesson here is to stay consistent and trust the process." ✅ "Ship the draft that embarrasses you slightly. That feeling is calibration, not warning."
End with the sharpest thing you have — not a restatement of your opening. If your ending mirrors your opening, you wasted the journey. The reader should arrive somewhere they couldn't have predicted from the first paragraph.
Subject line: Treat it as the hook for the hook. It must create curiosity without being clickbait. Curiosity comes from specificity and incompleteness — the reader senses there's something they need to know. Vague subject lines ("This week's thoughts") are invisible. Deceptive subject lines erode trust permanently.
Preview text: The second hook. Most writers leave it as the first line of the email. Write it deliberately — it should add to the subject line, not repeat it.
Length: As long as it needs to be. Not one word longer. The 10% rule applies: if your second draft is the same length as your first, you haven't cut enough.
Frequency: Consistency beats quality in the long run. A good newsletter published irregularly loses to a decent newsletter published every week. Show up. The audience is built by showing up.
After producing any draft, stop. Re-read core/anti-ai-rules.md Sections 1–7 with the draft in front of you. Go line by line through the pre-publish checklist in Section 7. Fix every failure before presenting the output.
Do not present a draft and note that it "may have some areas to refine." Fix them. The writer should receive a draft that has already cleared the checklist, not one that needs the checklist run on it by the writer.
core/anti-ai-rules.md?Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub deupaxx/everyday-writer --plugin ew